From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <413e5567550e94589ac35a4bbc4944c8@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: ip resolving From: "Russ Cox" In-Reply-To: <20030219154244.28769.qmail@mail.prosyst.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Wed, 19 Feb 2003 10:49:02 -0500 Topicbox-Message-UUID: 6a0cedae-eacb-11e9-9e20-41e7f4b1d025 how did those dns servers get there? at least under my vmware, dns is served by a vmware interface at .2, so i'd expect to see dns=192.168.79.2 it's possible that windows vmware dns is different from linux vmware dns, if you are running linux. plan 9's ndb/dnsdebug is like unix's dig. try this: g% ndb/dnsdebug > @192.168.233.2 www.google.com 1.1: sending to 192.168.233.2/192.168.233.2 www.google.com ip 1: rcvd OK from 192.168.233.2 (authoritative recurse can_recurse) Q: www.google.com ip Ans: www.google.com 5 min ip 216.239.37.101 Auth: google.com 3 day 13 hr 21 ns ns1.google.com google.com 3 day 13 hr 21 ns ns2.google.com google.com 3 day 13 hr 21 ns ns3.google.com google.com 3 day 13 hr 21 ns ns4.google.com Hint: ns1.google.com 1 day 12 hr 52 ip 216.239.32.10 ns2.google.com 1 day 12 hr 37 ip 216.239.34.10 ns3.google.com 1 day 12 hr 37 ip 216.239.36.10 ns4.google.com 1 day 12 hr 52 ip 216.239.38.10 ---------------------------- answer www.google.com 5 min ip 216.239.37.101 ---------------------------- > but use 192.168.79.2 instead of 192.168.233.2. then try with the dns servers listed in your /net/ndb. if the 192.168 dns server works but the two you have don't, then we can try to figure out how they got there. russ