www.seventeenorbust.com not resolvable

[Vato]

www.seventeenorbust.com is not resolvable to an IP in DNS :-(

use http://sb.pns.net instead for now

I'd recommend that whomever deals with the DNS for this project puts the domains on more widely spread DNS servers (like multiple continents...)

$ dig @k.gtld-servers.net. seventeenorbust.com. NS

; <<>> DiG 9.1.1 <<>> @k.gtld-servers.net. seventeenorbust.com. NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51023
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;seventeenorbust.com. IN NS

;; ANSWER SECTION:
seventeenorbust.com. 172800 IN NS ns1.qtm.net.
seventeenorbust.com. 172800 IN NS ns2.qtm.net.

;; ADDITIONAL SECTION:
ns1.qtm.net. 172800 IN A 216.163.32.51
ns2.qtm.net. 172800 IN A 216.163.32.52

;; Query time: 4 msec
;; SERVER: 192.52.178.30#53(k.gtld-servers.net.)
;; WHEN: Fri Nov 18 00:58:22 2005
;; MSG SIZE rcvd: 112

$ ping ns1.qtm.net.
ICMP Time exceeded in transit from 207.179.90.133
^C
$ ping ns2.qtm.net.
ICMP Time exceeded in transit from 207.179.90.133
^C

[Alien88]

I see no problem with it and as far as I know there weren't any issues with it - perhaps there was a temporary network problem.

If you see problems in the future, a traceroute helps moreso than a ping.

Thanks,
Mike

[Vato]

Agreed - it was past bedtime when this happened - but I should know better.
I did traceroute but forgot to post, and didn't keep a copy.
The issue was a routing loop somewhere in acd.net

5 ldn-bb2-pos1-3-0.telia.net (213.248.64.73) 0.583 ms 0.645 ms 0.496 ms
6 nyk-bb2-pos0-2-0.telia.net (213.248.65.94) 71.706 ms 71.377 ms 71.364 ms
7 ash-bb1-pos7-0-0-0.telia.net (213.248.80.138) 78.018 ms 77.561 ms 77.676 ms
8 williams-01995-ash-bb1.telia.net (213.248.88.10) 86.204 ms 77.627 ms 81.176 ms
9 hrndva1wcx2-pos0-0.wcg.net (64.200.89.49) 78.710 ms 78.667 ms 78.662 ms
10 brvwil1wcx3-pos4-0-oc192.wcg.net (64.200.249.18) 99.195 ms 96.737 ms 97.292 ms
11 brvwil1wcx2-pos1-0-oc192.wcg.net (64.200.236.77) 95.376 ms 95.482 ms 96.950 ms
12 dtrtmi1wce1-pos7-0.wcg.net (64.200.240.34) 100.992 ms 101.132 ms 102.444 ms
13 dtrtmi1wce1-acd-4-0.wcg.net (65.77.89.74) 103.576 ms 105.339 ms 103.725 ms
14 router.lnngmimn.acd.net (207.179.90.136) 118.179 ms 117.696 ms 118.544 ms
15 router.gdrpmibl.acd.net (207.179.120.50) 117.998 ms 117.920 ms 117.676 ms
16 216.163.46.82 (216.163.46.82) 113.780 ms 114.252 ms 113.697 ms
17 router.bnhrmiarlo1.qtm.net (216.163.46.85) 115.957 ms 117.481 ms 117.425 ms
18 bh-2948-eth.qtm.net (216.163.46.33) 115.830 ms 119.027 ms 116.137 ms
19 ns1.qtm.net (216.163.32.51) 114.231 ms 113.987 ms 118.857 ms

ie somewhere between hops 14 and 15.

acd.net appears to be single-homed to williams (or the backup routes are very pref'd down - which is OK) - 'sh ip bgp 216.163.32.51 | i _14103_' on route-views.oregon-ix.net

So the issue could have been a simple as a circuit outage - but DNS is supposed to be more resilient than that :-)

Nevermind...