From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461) Description of problem: When the named daemon is setup as a full DNS server, responding on behalf of clients, named always responds with 'Server Failed' when looking up 'wwws.sun.com'. As soon as the config is changed so named just forwards to ISP DNS servers, it finds the name just fine. This happens no matter what client I use (MS Win nslookup, dig from the box itself). Version-Release number of selected component (if applicable): bind-0.2.1-0.7x How reproducible: Always Steps to Reproduce: 1. Setup named with default root servers. 2. Run dig and try to lookup 'wwws.sun.com' Actual Results: client program responds with 'Server Failed', not sure what error that corresponds to in DNS protocol. Expected Results: client program should display the DNS entry Additional info: Network sniffs can be attached if needed. Configs can be attached, but I think there's nothing special there. Logs show nothing... did not try logs at debug level.
Created attachment 68406 [details] Log file from named during test (debug level 100)
Created attachment 68407 [details] Exact network sniff during test. Used tcpdump on the box itself
Not reproducable on RedHat 7.3 with same bind version. During the test used to create attachments, sever responded 'timed out' many times, then eventually responded 'server failed' on last query.
Upgrade to the current release.