dig vs resolv.conf
kalin at el.net
Mon Dec 27 05:47:20 UTC 2004
i have a machine that has only an ip address in it's resolv.conf like this:
if i do:
# dig @x.x.x.x somesite.com
this returns the correct answer right away.
if i do just:
# dig somesite.com
res_nsend to server default -- x.x.x.x: Operation timed out
i know that x.x.x.x has the authoritative records for somesite.com
the nameserver on x.x.x.x is BIND 9.2.1
can somebody please explain why is this happening.
i have to mention that i don't have a search specified in the resolv.conf.
does that matter? if so why?
More information about the bind-users