bug/feature in host/nslookup command - queries wrong server
Duncan Berriman
duncan at dcl.co.uk
Tue Feb 2 10:57:49 UTC 2010
Hi,
I have noticed that fedora 10 appears to ignore the server option when
using host or nslookup if the host in question is not available.
The commands should return no server available as they have in the past
but instead decide to query the local name server and return results
from that.
# nslookup google.co.uk 123.123.123.1
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: google.co.uk
Address: 66.102.11.99
Name: google.co.uk
Address: 66.102.11.104
# 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.104
google.co.uk has address 66.102.11.99
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.
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.
Using the debug option does not reveal anything it appears that the
command just decides since it can't connect to the server in question it
will query the servers defined in resolv.conf instead.
Is there an option in later release of fedora to enable/disable this? Is
it expected behaviour now?
Help!
Duncan
More information about the users
mailing list