It's my day for DNS questions :-) I have a DNS server in a small
office which serves up a local domain or two, and caches other
queries. One of the people in the office is a little miffed that for
some reason it won't resolve his dynamic address which is
dig @192.168.1.53 smurf.homeip.net
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
yet if you do
dig +trace @192.168.1.53 smurf.homeip.net
it returns an IP, albeit with a LONG (20s) delay after getting the
homeip.net NS addresses.
If you repeate the dig +trace immediately, it completes as fast as
you'd like it to. But if you do a regular dig just after a dig
+trace, it again fails, though I'd expect it to be cached.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!