* Re: [9fans] ip resolving
@ 2003-02-19 15:38 Russ Cox
2003-02-19 15:42 ` [9fans] " Nikolay Paskov
0 siblings, 1 reply; 10+ messages in thread
From: Russ Cox @ 2003-02-19 15:38 UTC (permalink / raw)
To: 9fans
what does cat /net/ndb show you?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [9fans] Re: ip resolving
2003-02-19 15:38 [9fans] " Russ Cox
@ 2003-02-19 15:42 ` Nikolay Paskov
2003-02-19 15:49 ` Russ Cox
0 siblings, 1 reply; 10+ messages in thread
From: Nikolay Paskov @ 2003-02-19 15:42 UTC (permalink / raw)
To: 9fans
Russ Cox writes:
> what does cat /net/ndb show you?
>
ip=192.168.79.128 ipmask=255.255.255.0 ipgw=192.168.79.2
dns=132.187.1.1
dns=132.187.1.3
Is that not enough ?
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [9fans] Re: ip resolving
2003-02-19 15:42 ` [9fans] " Nikolay Paskov
@ 2003-02-19 15:49 ` Russ Cox
2003-02-19 16:10 ` Nikolay Paskov
2003-02-19 16:45 ` andrey mirtchovski
0 siblings, 2 replies; 10+ messages in thread
From: Russ Cox @ 2003-02-19 15:49 UTC (permalink / raw)
To: 9fans
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [9fans] Re: ip resolving
2003-02-19 15:49 ` Russ Cox
@ 2003-02-19 16:10 ` Nikolay Paskov
2003-02-19 17:46 ` Russ Cox
2003-02-19 16:45 ` andrey mirtchovski
1 sibling, 1 reply; 10+ messages in thread
From: Nikolay Paskov @ 2003-02-19 16:10 UTC (permalink / raw)
To: 9fans
Now it works. Why I can't use 132.187.1.1 instead 192.168.79.2 ?
I have nat what is the problem?
Nikolay
Russ Cox writes:
> 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
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] Re: ip resolving
2003-02-19 16:10 ` Nikolay Paskov
@ 2003-02-19 17:46 ` Russ Cox
2003-02-20 10:13 ` Nikolay Paskov
0 siblings, 1 reply; 10+ messages in thread
From: Russ Cox @ 2003-02-19 17:46 UTC (permalink / raw)
To: 9fans
> Now it works. Why I can't use 132.187.1.1 instead 192.168.79.2 ?
> I have nat what is the problem?
did you change it manually to 132.187.1.1?
i have a hard time believing vmware set it to that.
how did it get set to 132.187.1.1 in the first place?
first of all, 132.187.1.1 is likely to be a router
rather than a dns server. vmware may be blocking
dns packets except the ones to itself. i don't know.
just use the vmware ones.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [9fans] Re: ip resolving
2003-02-19 17:46 ` Russ Cox
@ 2003-02-20 10:13 ` Nikolay Paskov
2003-02-20 14:24 ` Russ Cox
0 siblings, 1 reply; 10+ messages in thread
From: Nikolay Paskov @ 2003-02-20 10:13 UTC (permalink / raw)
To: 9fans
Russ Cox writes:
>> Now it works. Why I can't use 132.187.1.1 instead 192.168.79.2 ?
>> I have nat what is the problem?
>
> did you change it manually to 132.187.1.1?
> i have a hard time believing vmware set it to that.
> how did it get set to 132.187.1.1 in the first place?
>
> first of all, 132.187.1.1 is likely to be a router
> rather than a dns server. vmware may be blocking
> dns packets except the ones to itself. i don't know.
> just use the vmware ones.
>
No, 132.187.1.1 is not a router I'm using it as DNS server on my linux box.
I changed it manually of course. But may be you are right about blocking
from vmware side. I have to check this. BTW now I have a problem with the
DHCP server. Nothing is changed in configuration only rebooted and now I
have no response from the DHCP server.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] Re: ip resolving
2003-02-20 10:13 ` Nikolay Paskov
@ 2003-02-20 14:24 ` Russ Cox
2003-02-20 14:35 ` Nikolay Paskov
0 siblings, 1 reply; 10+ messages in thread
From: Russ Cox @ 2003-02-20 14:24 UTC (permalink / raw)
To: 9fans
> No, 132.187.1.1 is not a router I'm using it as DNS server on my linux box.
> I changed it manually of course. But may be you are right about blocking
> from vmware side. I have to check this. BTW now I have a problem with the
> DHCP server. Nothing is changed in configuration only rebooted and now I
> have no response from the DHCP server.
reboot again. there appears to be a bug in the
new ip drop-if-no-default-route code.
russ
^ permalink raw reply [flat|nested] 10+ messages in thread
* [9fans] Re: ip resolving
2003-02-20 14:24 ` Russ Cox
@ 2003-02-20 14:35 ` Nikolay Paskov
0 siblings, 0 replies; 10+ messages in thread
From: Nikolay Paskov @ 2003-02-20 14:35 UTC (permalink / raw)
To: 9fans
Russ Cox writes:
>> No, 132.187.1.1 is not a router I'm using it as DNS server on my linux box.
>> I changed it manually of course. But may be you are right about blocking
>> from vmware side. I have to check this. BTW now I have a problem with the
>> DHCP server. Nothing is changed in configuration only rebooted and now I
>> have no response from the DHCP server.
>
> reboot again. there appears to be a bug in the
> new ip drop-if-no-default-route code.
I did but nothing still the same mistake.
Nikolay
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [9fans] Re: ip resolving
2003-02-19 15:49 ` Russ Cox
2003-02-19 16:10 ` Nikolay Paskov
@ 2003-02-19 16:45 ` andrey mirtchovski
1 sibling, 0 replies; 10+ messages in thread
From: andrey mirtchovski @ 2003-02-19 16:45 UTC (permalink / raw)
To: 9fans
On Wed, 19 Feb 2003, Russ Cox wrote:
> it's possible that windows vmware dns is different
> from linux vmware dns, if you are running linux.
>
my linux vmware has the following for dns (straight boot, haven't touched
anything in the configuration except uncomment ip/ipconfig in termrc):
term% cat /net/ndb
ip=192.168.215.128 ipmask=255.255.255.0 ipgw=192.168.215.2
dom=.localdomain
dns=192.168.215.2
term%
at least 2.0 asks the user whether they want to bridge the interface or use
NAT. my ethernet setting is NAT...
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2003-02-20 14:35 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <3291755392@snellwilcox.com>
2003-02-19 15:44 ` [9fans] ip resolving Steve Simon
2003-02-19 15:50 ` [9fans] " Nikolay Paskov
2003-02-19 15:38 [9fans] " Russ Cox
2003-02-19 15:42 ` [9fans] " Nikolay Paskov
2003-02-19 15:49 ` Russ Cox
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
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).