North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

BTinternet problems?

  • From: Mike
  • Date: Tue Jun 17 13:09:22 2003


We're receiving multiple complaints about problems reaching anything @bt. Is anyone else experiencing this?

I.E. e-mails to @btopenworld and also @btinternet.com are bouncing. The root cause seems that we are unable to resolve anything within bt.com et al. For whatever reason, this is affecting all of the netblocks that we have nameservers in, but not some others we control.

I.E. working ok from 204.188.96.0/20:

% dig @194.72.6.52 bt.com | grep ^bt
bt.com. 1D IN A 62.7.244.126
bt.com. 1D IN NS dns1.axion.bt.co.uk.
bt.com. 1D IN NS ns1.bt.net.
bt.com. 1D IN NS dns0.axion.bt.co.uk.


Not working at all within 208.139.192.0/20:

ns2# dig @194.72.6.52 bt.com

; <<>> DiG 9.2.1 <<>> @194.72.6.52 bt.com
;; global options: printcmd
;; connection timed out; no servers could be reached

At the same time...

ns2# tcpdump -n -s 1600 host 194.72.6.52
tcpdump: listening on xl0
10:40:07.235635 208.139.192.2.36647 > 194.72.6.52.53: 17495+ A? bt.com. (24)
10:40:12.241697 208.139.192.2.36647 > 194.72.6.52.53: 17495+ A? bt.com. (24)



ns2# traceroute 194.72.6.52
traceroute to 194.72.6.52 (194.72.6.52), 64 hops max, 40 byte packets
1 cw-gw (208.139.192.1) 1.255 ms 5.908 ms 1.216 ms
2 denver-core-fe-0-0 (206.168.230.5) 7.285 ms 2.721 ms 2.597 ms
3 den1cspdaa02-v200.denver.terabeam.net (216.137.18.229) 4.406 ms 2.355 ms 6.978 ms
4 den1mcoraa01-ge110-v101.denver.terabeam.net (216.137.17.149) 1.261 ms 4.901 ms 7.538 ms
5 den1pcinaa01-ge020.denver.terabeam.net (216.137.17.21) 5.450 ms 6.128 ms 7.533 ms
6 12.124.158.25 (12.124.158.25) 1.163 ms 1.572 ms 4.476 ms
7 gbr1-p60.dvmco.ip.att.net (12.123.36.138) 2.529 ms 1.285 ms 6.739 ms
8 gbr4-p70.dvmco.ip.att.net (12.122.5.21) 1.365 ms 3.114 ms 4.32 ms
9 12.122.10.117 (12.122.10.117) 22.911 ms 19.350 ms 19.352 ms
10 tbr1-p012301.n54ny.ip.att.net (12.122.10.1) 38.500 ms 38.203 ms 44.327 ms
11 gar4-p300.n54ny.ip.att.net (12.123.3.2) 37.844 ms 37.614 ms 42.708 ms
12 12.126.124.82 (12.126.124.82) 39.463 ms 39.453 ms 39.360 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I've fiddled with our routes here, tried from different netblocks to no avail. Don't see any mention of bt at the puck.nether.net NOC list either. Thought about sending them mail, but wound up back at step #1 above...