Red Hat Bugzilla – Bug 71693
New bind-9.2.1 package breaks mail delivery
Last modified: 2007-04-18 12:45:35 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: The new bind-9.2.1 package for 7.0 seems to break the resolver. Sendmail just put stuff in the mail queue instead of sending it due to name server timeout. Version-Release number of selected component (if applicable): How reproducible: Didn't try Steps to Reproduce: 1. I used up2date on our 7.0 firewall system to update our packages including the kernel. 2. Updated the /etc/sysconfig/named file to point at the chroot environment. 3. Disabled IP-v6 support (by putting "listen-ip-v6 { none; };" in the options section of the config file) when the resolver refused to work at all and got partial sucess. The "host" command would work but email still wound up in the queue instead of being sent. Additional info: All packages were updated to the current errata releases as of 8/14/02. The system in question is an SMP with 2 processors. I've corrected the problem by reverting the bind* pacakges back to the 8.2.2_P5 releases. Since this is a critical path system I can't have it down to continue the debug process. Sorry.
Not reproducable on any of my test machines.
Hmmmm. OK let's see if some additional info will help. The system is a firewall that uses the split DNS setup whereby the firewall is running bind and supplies address resolution to the outside world while there is a seperate DNS server on the inside LAN that provides resolution for local addresses. This inside DNS server is set to forward unresolvable address lookups to the firewall which then goes out on the internet to resolve them. The firewall's resolv.conf points to the inside DNS server. If the lookup is for an external address the request goes to the internal server then back to the firewall which performs the lookup. Does this make sense to you? In any case this works fine with bind-8.2.2_P5-25 but does not work at all with the bind-9.2.1 package.
Closing since this bug has not been reproduced in a couple of years.