Hi, In certain versions of linux I have noticed that the host/nslookup and dig command query the wrong server.
For instance if the following command is run it should return ;; connection timed out; no servers could be reached # host google.co.uk 123.123.123.1 However on certain versions of linux it decides almost instantly since it can't connect to the server specified it will use the name servers in resolv.conf, in this case that is the local host. # host google.co.uk 123.123.123.1 Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: google.co.uk has address 66.102.11.99 google.co.uk has address 66.102.11.104 google.co.uk mail is handled by 10 google.com.s9a1.psmtp.com. google.co.uk mail is handled by 10 google.com.s9a2.psmtp.com. google.co.uk mail is handled by 10 google.com.s9b1.psmtp.com. google.co.uk mail is handled by 10 google.com.s9b2.psmtp.com. This is clearly not expected behaviour and would therefore appear to be a bug. The problem can be reproduced in CentOS release 5.4 (Final) and Fedora 10, which appear to use bind versions 9.3.6-4.P1.el5_4.2 and 9.5.1-2.P2.fc10.i386. Early and later versions of Fedora work as expected and return an error. I had expected both would be running the same version of bind and am surprised that they are so different. Any idea how the correct behaviour can be reinstated and why it is happening. Apologies if this is the wrong place to ask but it would appear to be a bind issue. Thanks Duncan _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
