dns problem with plan9.iso downloaded on Tue07Feb2012_2219

[ROuNIN]

Hello
Using this new version and creating a new Plan9 install with the
following:

md5sum /home/plan9/plan9.Tue07Feb2012_2219.iso
a62dba17efa51e3c5dbd1b12e8586492 /home/plan9/
plan9.Tue07Feb2012_2219.iso

I see the following:

term% ip/ipconfig
term% ndb/dns -r
term% ip/ping www.google.com
ip/ping: couldn't dial icmp!www.google.com!1: cs: temporary problem:
dns: dns failure
term% ip/ping -fr 192.168.0.12
sending 32 64 byte messages 0 ms apart to icmp!192.168.0.12!1
0: rtt 9358 µs, avg rtt 9358 µs, ttl = 64
1: rtt 11086 µs, avg rtt 10222 µs, ttl = 64
2: rtt 15649 µs, avg rtt 12031 µs, ttl = 64
3: rtt 18320 µs, avg rtt 13603 µs, ttl = 64
4: rtt 19911 µs, avg rtt 14864 µs, ttl = 64
5: rtt 21464 µs, avg rtt 15964 µs, ttl = 64
6: rtt 23002 µs, avg rtt 16970 µs, ttl = 64
7: rtt 24553 µs, avg rtt 17917 µs, ttl = 64
8: rtt 26140 µs, avg rtt 18831 µs, ttl = 64
9: rtt 27737 µs, avg rtt 19722 µs, ttl = 64
10: rtt 29308 µs, avg rtt 20593 µs, ttl = 64
11: rtt 30801 µs, avg rtt 21444 µs, ttl = 64
12: rtt 32311 µs, avg rtt 22280 µs, ttl = 64
13: rtt 33893 µs, avg rtt 23109 µs, ttl = 64
14: rtt 35401 µs, avg rtt 23928 µs, ttl = 64
15: rtt 36926 µs, avg rtt 24741 µs, ttl = 64
16: rtt 38423 µs, avg rtt 25546 µs, ttl = 64
17: rtt 39773 µs, avg rtt 26336 µs, ttl = 64
18: rtt 41220 µs, avg rtt 27119 µs, ttl = 64
19: rtt 42084 µs, avg rtt 27868 µs, ttl = 64
20: rtt 44871 µs, avg rtt 28677 µs, ttl = 64
21: rtt 45633 µs, avg rtt 29448 µs, ttl = 64
22: rtt 46443 µs, avg rtt 30187 µs, ttl = 64
23: rtt 47241 µs, avg rtt 30897 µs, ttl = 64
24: rtt 48466 µs, avg rtt 31600 µs, ttl = 64
25: rtt 49489 µs, avg rtt 32288 µs, ttl = 64
26: rtt 50463 µs, avg rtt 32961 µs, ttl 5= 64
27: rtt 52125 µs, avg rtt 33646 µs, ttl = 64
28: rtt 53155 µs, avg rtt 34318 µs, ttl = 64
29: rtt 54089 µs, avg rtt 34977 µs, ttl = 64
30: rtt 55183 µs, avg rtt 35629 µs, ttl = 64
31: rtt 56200 µs, avg rtt 36272 µs, ttl = 64
term% ip/ping www.bbc.co.uk
ip/ping: couldn't dial icmp!www.bbc.co.uk!1: cs: temporary problem:
dns: dns failure
term%

It used to work before - what happened?
Have I missed something?
ROuNIN

[Sergey Zhilkin]

is ndb/cs running ? stat /srv/cs

Post by ROuNIN
Hello
Using this new version and creating a new Plan9 install with the
md5sum /home/plan9/plan9.Tue07Feb2012_2219.iso
a62dba17efa51e3c5dbd1b12e8586492 /home/plan9/
plan9.Tue07Feb2012_2219.iso
term% ip/ipconfig
term% ndb/dns -r
term% ip/ping www.google.com
dns: dns failure
term% ip/ping -fr 192.168.0.12
sending 32 64 byte messages 0 ms apart to icmp!192.168.0.12!1
0: rtt 9358 µs, avg rtt 9358 µs, ttl = 64
1: rtt 11086 µs, avg rtt 10222 µs, ttl = 64
2: rtt 15649 µs, avg rtt 12031 µs, ttl = 64
3: rtt 18320 µs, avg rtt 13603 µs, ttl = 64
4: rtt 19911 µs, avg rtt 14864 µs, ttl = 64
5: rtt 21464 µs, avg rtt 15964 µs, ttl = 64
6: rtt 23002 µs, avg rtt 16970 µs, ttl = 64
7: rtt 24553 µs, avg rtt 17917 µs, ttl = 64
8: rtt 26140 µs, avg rtt 18831 µs, ttl = 64
9: rtt 27737 µs, avg rtt 19722 µs, ttl = 64
10: rtt 29308 µs, avg rtt 20593 µs, ttl = 64
11: rtt 30801 µs, avg rtt 21444 µs, ttl = 64
12: rtt 32311 µs, avg rtt 22280 µs, ttl = 64
13: rtt 33893 µs, avg rtt 23109 µs, ttl = 64
14: rtt 35401 µs, avg rtt 23928 µs, ttl = 64
15: rtt 36926 µs, avg rtt 24741 µs, ttl = 64
16: rtt 38423 µs, avg rtt 25546 µs, ttl = 64
17: rtt 39773 µs, avg rtt 26336 µs, ttl = 64
18: rtt 41220 µs, avg rtt 27119 µs, ttl = 64
19: rtt 42084 µs, avg rtt 27868 µs, ttl = 64
20: rtt 44871 µs, avg rtt 28677 µs, ttl = 64
21: rtt 45633 µs, avg rtt 29448 µs, ttl = 64
22: rtt 46443 µs, avg rtt 30187 µs, ttl = 64
23: rtt 47241 µs, avg rtt 30897 µs, ttl = 64
24: rtt 48466 µs, avg rtt 31600 µs, ttl = 64
25: rtt 49489 µs, avg rtt 32288 µs, ttl = 64
26: rtt 50463 µs, avg rtt 32961 µs, ttl 5= 64
27: rtt 52125 µs, avg rtt 33646 µs, ttl = 64
28: rtt 53155 µs, avg rtt 34318 µs, ttl = 64
29: rtt 54089 µs, avg rtt 34977 µs, ttl = 64
30: rtt 55183 µs, avg rtt 35629 µs, ttl = 64
31: rtt 56200 µs, avg rtt 36272 µs, ttl = 64
term% ip/ping www.bbc.co.uk
dns: dns failure
term%
It used to work before - what happened?
Have I missed something?
ROuNIN

[erik quanstrom]

Post by ROuNIN
term% ip/ping -fr 192.168.0.12

192.168.0.12 is not a routable address, so one
onders if you can actually route out of your local
segment. try 8.8.8.8.

Post by ROuNIN
It used to work before - what happened?
Have I missed something?
ROuNIN

"dns failure" usually means that a dns message came
back in response to your query that had SRVFAIL
set.

so i'd wonder if you're using an external dns that's
failing.

comparing the results from ndb/dnsquery (using the
standard lookup mechanisms) and ndb/debug (querying
down from the root) should be enough to tell you if
the problem is local or remote.

- erik

[ROuNIN]

Hello all,
Thank you. Managed to ping 8.8.8.8 and had to recompile ping after
modifying nrand.c as per my earlier bug find
on Mar 9 2009, 9:38 am
[
http://groups.google.com/group/comp.os.plan9/browse_thread/thread/ac738207e85e04eb/b378c7677969d241?lnk=gst&q=ping++suicide%3A+sys%3A+trap%3A+divide+error#b378c7677969d241
]

term% ip/ping -fr 8.8.8.8
sending 32 64 byte messages 0 ms apart to icmp!8.8.8.8!1
ping 251: suicide: sys: trap: divide error pc=0x0000395e
term% 0: rtt 42099 µs, avg rtt 42099 µs, ttl = 50

term% stat /srv/cs
stat: '/bin/stat' file does not exist
term% ip/ping -fr 192.168.0.12
sending 32 64 byte messages 0 ms apart to icmp!192.168.0.12!1
ping 255: suicide: sys: trap: divide error pc=0x0000395e
term% 0: rtt 12618 µs, avg rtt 12618 µs, ttl = 64

term% ip/ping -fr 192.168.0.12
sending 32 64 byte messages 0 ms apart to icmp!192.168.0.12!1
0: rtt 5167 µs, avg rtt 5167 µs, ttl = 64
1: rtt 7067 µs, avg rtt 6117 µs, ttl = 64
2: rtt 9645 µs, avg rtt 7293 µs, ttl = 64
3: rtt 10735 µs, avg rtt 8153 µs, ttl = 64
4: rtt 13051 µs, avg rtt 9133 µs, ttl = 64
5: rtt 14816 µs, avg rtt 10080 µs, ttl = 64
6: rtt 16150 µs, avg rtt 10947 µs, ttl = 64
7: rtt 17569 µs, avg rtt 11775 µs, ttl = 64
8: rtt 18997 µs, avg rtt 12577 µs, ttl = 64
9: rtt 20061 µs, avg rtt 13325 µs, ttl = 64
10: rtt 21368 µs, avg rtt 14056 µs, ttl = 64
11: rtt 22437 µs, avg rtt 14755 µs, ttl = 64
12: rtt 23568 µs, avg rtt 15433 µs, ttl = 64
13: rtt 24623 µs, avg rtt 16089 µs, ttl = 64
14: rtt 26301 µs, avg rtt 16770 µs, ttl = 64
15: rtt 27379 µs, avg rtt 17433 µs, ttl = 64
16: rtt 28490 µs, avg rtt 18083 µs, ttl = 64
17: rtt 29563 µs, avg rtt 18721 µs, ttl = 64
18: rtt 30658 µs, avg rtt 19349 µs, ttl = 64
19: rtt 31862 µs, avg rtt 19975 µs, ttl = 64
20: rtt 33241 µs, avg rtt 20607 µs, ttl = 64
21: rtt 34314 µs, avg rtt 21230 µs, ttl = 64
22: rtt 35416 µs, avg rtt 21846 µs, ttl = 64
23: rtt 37885 µs, avg rtt 22515 µs, ttl = 64
24: rtt 38992 µs, avg rtt 23174 µs, ttl = 64
25: rtt 40022 µs, avg rtt 23822 µs, ttl = 64
26: rtt 43156 µs, avg rtt 24538 µs, ttl = 64
27: rtt 44253 µs, avg rtt 25242 µs, ttl = 64
28: rtt 45420 µs, avg rtt 25938 µs, ttl = 64
29: rtt 46566 µs, avg rtt 26625 µs, ttl = 64
30: rtt 47638 µs, avg rtt 27303 µs, ttl = 64
31: rtt 48711 µs, avg rtt 27972 µs, ttl = 64
term%
term% ip/ping -fr 8.8.8.8
sending 32 64 byte messages 0 ms apart to icmp!8.8.8.8!1
0: rtt 42884 µs, avg rtt 42884 µs, ttl = 50
1: rtt 48407 µs, avg rtt 45645 µs, ttl = 50
2: rtt 55391 µs, avg rtt 48894 µs, ttl = 50
3: rtt 60531 µs, avg rtt 51803 µs, ttl = 50
4: rtt 61919 µs, avg rtt 53826 µs, ttl = 50
5: rtt 62990 µs, avg rtt 55353 µs, ttl = 50
6: rtt 64305 µs, avg rtt 56632 µs, ttl = 50
8: rtt 65482 µs, avg rtt 57738 µs, ttl = 50
10: rtt 66707 µs, avg rtt 58735 µs, ttl = 50
7: rtt 68365 µs, avg rtt 59698 µs, ttl = 50
9: rtt 80852 µs, avg rtt 61621 µs, ttl = 50
13: rtt 81501 µs, avg rtt 63277 µs, ttl = 50
12: rtt 82333 µs, avg rtt 64743 µs, ttl = 50
11: rtt 83147 µs, avg rtt 66058 µs, ttl = 50
15: rtt 83659 µs, avg rtt 67231 µs, ttl = 50
14: rtt 84934 µs, avg rtt 68337 µs, ttl = 50
16: rtt 85564 µs, avg rtt 69351 µs, ttl = 50
18: rtt 86256 µs, avg rtt 70290 µs, ttl = 50
17: rtt 87047 µs, avg rtt 71172 µs, ttl = 50
21: rtt 87995 µs, avg rtt 72013 µs, ttl = 50
19: rtt 88954 µs, avg rtt 72820 µs, ttl = 50
20: rtt 90266 µs, avg rtt 73613 µs, ttl = 50
24: rtt 90952 µs, avg rtt 74367 µs, ttl = 50
22: rtt 91914 µs, avg rtt 75098 µs, ttl = 50
25: rtt 92650 µs, avg rtt 75800 µs, ttl = 50
23: rtt 93675 µs, avg rtt 76487 µs, ttl = 50
27: rtt 94348 µs, avg rtt 77149 µs, ttl = 50
26: rtt 95763 µs, avg rtt 77813 µs, ttl = 50
28: rtt 98331 µs, avg rtt 78521 µs, ttl = 50
29: rtt 99228 µs, avg rtt 79211 µs, ttl = 50
30: rtt 100104 µs, avg rtt 79885 µs, ttl = 50
31: rtt 100916 µs, avg rtt 80542 µs, ttl = 50
term% ip/ping www.google.com
ip/ping: couldn't dial icmp!www.google.com!1: cs: temporary problem:
dns: dns failure
term%

192.168.0.12 is my NAS box on my network.

Can you help? I don't know how to rectify this DNS problem.
ROuNIN

[erik quanstrom]

Post by ROuNIN
Thank you. Managed to ping 8.8.8.8 and had to recompile ping after
modifying nrand.c as per my earlier bug find
on Mar 9 2009, 9:38 am
[
http://groups.google.com/group/comp.os.plan9/browse_thread/thread/ac738207e85e04eb/b378c7677969d241?lnk=gst&q=ping++suicide%3A+sys%3A+trap%3A+divide+error#b378c7677969d241
]
term% ip/ping -fr 8.8.8.8
sending 32 64 byte messages 0 ms apart to icmp!8.8.8.8!1
ping 251: suicide: sys: trap: divide error pc=0x0000395e
term% 0: rtt 42099 µs, avg rtt 42099 µs, ttl = 50

this was fixed years ago. see for yourself.
9fs sources && /n/sources/plan9/386/bin/ip/ping -fr 8.8.8.8

- erik