From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: ip resolving
Date: Wed, 19 Feb 2003 10:49:02 -0500 [thread overview]
Message-ID: <413e5567550e94589ac35a4bbc4944c8@plan9.bell-labs.com> (raw)
In-Reply-To: <20030219154244.28769.qmail@mail.prosyst.com>
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
next prev parent reply other threads:[~2003-02-19 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 15:31 [9fans] " Nikolay Paskov
2003-02-19 15:38 ` Russ Cox
2003-02-19 15:42 ` [9fans] " Nikolay Paskov
2003-02-19 15:49 ` Russ Cox [this message]
2003-02-19 16:10 ` Nikolay Paskov
2003-02-19 17:46 ` Russ Cox
2003-02-20 10:13 ` Nikolay Paskov
2003-02-20 14:24 ` Russ Cox
2003-02-20 14:35 ` Nikolay Paskov
2003-02-19 16:45 ` andrey mirtchovski
2003-02-19 15:44 [9fans] " Steve Simon
2003-02-19 15:50 ` [9fans] " Nikolay Paskov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=413e5567550e94589ac35a4bbc4944c8@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).