[9fans] puzzling dnsdebug behavior

[9fans] puzzling dnsdebug behavior

[peh]

I'm puzzled by the following:

term% ndb/dnsquery
> scylla.internal.us-celstream.com
scylla.internal.us-celstream.com ip	192.168.10.1
> term% ndb/dnsdebug @scylla.internal.us-celstream.com www.flcimages.com
can't resolve scylla.internal.us-celstream.com
term% ndb/dnsdebug @192.168.10.1 www.flcimages.com
1.1: sending to 192.168.10.1/192.168.10.1 www.flcimages.com ip
1: rcvd OK from 192.168.10.1 ( recurse can_recurse)
	Q:    www.flcimages.com ip
	Ans:  www.flcimages.com                16 min 37 sec   ip   	64.232.217.228
	Auth: flcimages.com                    1 day 21 hr 57  ns   	DNS1.COLORTECHNOLOGY.com
	      flcimages.com                    1 day 21 hr 57  ns   	DNS.COLORTECHNOLOGY.com
	Hint: DNS1.COLORTECHNOLOGY.com         4 hr 41 min 1 s ip   	207.225.69.130
	      DNS.COLORTECHNOLOGY.com          4 hr 25 min 29  ip   	207.225.69.129
----------------------------
answer www.flcimages.com                16 min 37 sec   ip   	64.232.217.228
----------------------------
term% 

Thanks for the help,
Pat

Re: [9fans] puzzling dnsdebug behavior

[presotto]

Dnsdebug doesn't use the local dns server to resolve anything.
It always starts from what it finds in /lib/ndb/local.
If /lib/ndb/local isn't set up to point to a root server, it
may not be able to find anything.

Dnsquery uses the local dns server to find things.  How that
server is set up decides how things are found.  If you've
started it with the -r option, it may be acting only as a
resolver and forwarding all requests somewhere else.

To figure out what's really happening:
1) what's in /lib/ndb/local
2) what's in /net/ndb
3) how what ndb/dns started