From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2 Description of problem: 46 hours after I upgraded my server (2xPIII using FC3) fetchmail started failing with the following error in the log: fetchmail: fetchmail: getaddrinfo(pop-server.san.rr.com.pop3) fetchmail: Query status=2 (SOCKET) Fetchmail kept running, but reported this error every cycle rather than downloading any mail. Once restarted, the additional error message fetchmail: couldn't find canonical DNS name of pop-server.san.rr.com (pop-server.san.rr.com) fetchmail: Query status=11 (DNS) occurs at the beginning of every cycle. I thought it might be a binary ABI incompatibility so I rebuilt fetchmail from the canonical source rpm. The rebuilt fetchmail works, but does continue to report the DNS error on every cycle. Fetchmail is started from an init script as: daemon fetchmail -d 900 -t 600 -f /etc/fetchmail.conf -L /var/log/fetchmail The configuration file has not been modified for 2 years. Version-Release number of selected component (if applicable): fetchmail-6.2.5-6 How reproducible: Always Steps to Reproduce: 1. Update FC3 to latest ("yum update") 2. Restart fetchmail 3. Actual Results: fetchmail: starting fetchmail 6.2.5 daemon fetchmail: couldn't find canonical DNS name of pop-server.san.rr.com (pop-server.san.rr.com) fetchmail: Query status=11 (DNS) fetchmail: fetchmail: getaddrinfo(pop-server.san.rr.com.pop3) fetchmail: Query status=2 (SOCKET) fetchmail: fetchmail: getaddrinfo(pop-server.san.rr.com.pop3) fetchmail: Query status=2 (SOCKET) Expected Results: fetchmail: starting fetchmail 6.2.5 daemon fetchmail: 22 messages for mattc at pop-server.san.rr.com (161557 octets). Additional info: I rebuild fetchmail using the source rpm (from http://www.catb.org/~esr/fetchmail/) and that version works.
The fetchmail shipped in FC3 does not use bind-libs at all, this could not have had any influence. Testing the relevant lookup code works here fine; this really looks like a temporary DNS failure that went away roughly at the time you have rebuilt the SRPM.