.ORG DNS Problem?

Anybody else having problems resolving .ORG domains via TLD1.ULTRADNS.NET
(204.74.112.1) and TLD2.ULTRADNS.NET. (204.74.113.1). I'm seeing slow respones,
or no responses.

Traceroutes look fine:

% tcptraceroute 204.74.112.1 53
Selected device fxp0, address 64.246.100.1, port 55786 for outgoing packets
Tracing the path to 204.74.112.1 on TCP port 53, 30 hops max
1 fastethernet-0-0.angola-gw.amplex.net (64.246.100.126) 9.403 ms 7.361 ms
9.148 ms
2 dtrtmi1wce1-ser2-5-5.wcg.net (65.77.89.53) 9.801 ms 8.061 ms 9.917 ms
3 brvwil1wcx2-pos14-1.wcg.net (64.200.240.33) 9.748 ms 8.341 ms 9.612 ms
4 chcgil9lcx1-pos6-0-oc48.wcg.net (64.200.103.118) 10.001 ms 9.172 ms 8.762 ms
5 ge-4-3-0.r00.chcgil06.us.bb.verio.net (206.223.119.12) 9.646 ms 8.960 ms
9.502 ms
6 ge-0-3-0.r02.chcgil06.us.bb.verio.net (129.250.2.121) 9.323 ms 9.071 ms
9.039 ms
7 ge-1-1.a00.chcgil07.us.ra.verio.net (129.250.25.136) 9.848 ms 9.306 ms
9.003 ms
8 fa-2-1.a00.chcgil07.us.ce.verio.net (128.242.186.134) 9.679 ms 9.697 ms
9.684 ms
9 tld1.ultradns.net (204.74.112.1) [open] 10.296 ms 10.625 ms 9.537 ms

-AND -

% tcptraceroute 204.74.113.1 53
Selected device fxp0, address 64.246.100.1, port 55792 for outgoing packets
Tracing the path to 204.74.113.1 on TCP port 53, 30 hops max
1 fastethernet-0-0.angola-gw.amplex.net (64.246.100.126) 5.402 ms 7.282 ms
9.738 ms
2 dtrtmi1wce1-ser2-5-5.wcg.net (65.77.89.53) 9.973 ms 7.958 ms 9.909 ms
3 brvwil1wcx2-pos14-1.wcg.net (64.200.240.33) 9.800 ms 10.295 ms 8.835 ms
4 chcgil9lcx1-pos6-0-oc48.wcg.net (64.200.103.118) 8.878 ms 8.786 ms 9.187 ms
5 fe9-2.IR1.Chicago2-IL.us.xo.net (206.111.2.149) 9.512 ms 8.964 ms 8.869 ms
6 p5-0-0.RAR2.Chicago-IL.us.xo.net (65.106.6.137) 9.580 ms 9.214 ms 9.120 ms
7 p4-1-0.MAR2.Chicago-IL.us.xo.net (65.106.6.154) 9.512 ms 10.285 ms 9.594 ms
8 p15-0.CHR1.Chicago-IL.us.xo.net (207.88.84.14) 10.126 ms 9.517 ms 9.472 ms
9 10.11.102.1 (10.11.102.1) 10.990 ms 9.808 ms 10.182 ms
10 tld2.ultradns.net (204.74.113.1) [open] 9.933 ms 10.124 ms 9.778 ms

Source IP for the traceroutes is 64.246.100.1.

Dig's don't get very far:

% dig nanog.org +trace

; <<>> DiG 9.2.2-P3 <<>> nanog.org +trace
;; global options: printcmd
. 300086 IN NS C.ROOT-SERVERS.NET.
. 300086 IN NS D.ROOT-SERVERS.NET.
. 300086 IN NS E.ROOT-SERVERS.NET.
. 300086 IN NS F.ROOT-SERVERS.NET.
. 300086 IN NS G.ROOT-SERVERS.NET.
. 300086 IN NS H.ROOT-SERVERS.NET.
. 300086 IN NS I.ROOT-SERVERS.NET.
. 300086 IN NS J.ROOT-SERVERS.NET.
. 300086 IN NS K.ROOT-SERVERS.NET.
. 300086 IN NS L.ROOT-SERVERS.NET.
. 300086 IN NS M.ROOT-SERVERS.NET.
. 300086 IN NS A.ROOT-SERVERS.NET.
. 300086 IN NS B.ROOT-SERVERS.NET.
;; Received 388 bytes from 64.246.100.1#53(64.246.100.1) in 10 ms

org. 172800 IN NS TLD1.ULTRADNS.NET.
org. 172800 IN NS TLD2.ULTRADNS.NET.
;; Received 109 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 9 ms

;; connection timed out; no servers could be reached

-Adam

Seems to be working fine now:

% dig nanog.org ns +trace

; <<>> DiG 9.2.2-P3 <<>> nanog.org ns +trace
;; global options: printcmd
. 298767 IN NS C.ROOT-SERVERS.NET.
. 298767 IN NS D.ROOT-SERVERS.NET.
. 298767 IN NS E.ROOT-SERVERS.NET.
. 298767 IN NS F.ROOT-SERVERS.NET.
. 298767 IN NS G.ROOT-SERVERS.NET.
. 298767 IN NS H.ROOT-SERVERS.NET.
. 298767 IN NS I.ROOT-SERVERS.NET.
. 298767 IN NS J.ROOT-SERVERS.NET.
. 298767 IN NS K.ROOT-SERVERS.NET.
. 298767 IN NS L.ROOT-SERVERS.NET.
. 298767 IN NS M.ROOT-SERVERS.NET.
. 298767 IN NS A.ROOT-SERVERS.NET.
. 298767 IN NS B.ROOT-SERVERS.NET.
;; Received 404 bytes from 64.246.100.1#53(64.246.100.1) in 4 ms

org. 172800 IN NS TLD1.ULTRADNS.NET.
org. 172800 IN NS TLD2.ULTRADNS.NET.
;; Received 109 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 9 ms

NANOG.ORG. 172800 IN NS DNS2.MERIT.NET.
NANOG.ORG. 172800 IN NS DNS.MERIT.NET.
NANOG.ORG. 172800 IN NS DNS3.MERIT.NET.
ORG. 86400 IN NS TLD2.ULTRADNS.NET.
ORG. 86400 IN NS TLD1.ULTRADNS.NET.
;; Received 180 bytes from 204.74.112.1#53(TLD1.ULTRADNS.NET) in 10 ms

-Adam

Quoting Adam Kujawski <adamkuj@amplex.net>:

Hi,

...on Thu, Jun 24, 2004 at 11:18:26AM -0400, Adam Kujawski wrote:

> Anybody else having problems resolving .ORG domains via TLD1.ULTRADNS.NET
> (204.74.112.1) and TLD2.ULTRADNS.NET. (204.74.113.1). I'm seeing slow
> respones, or no responses.

Same here, until a few minutes ago. Didn't work
(connection timed out) from various places in
Europe, while I had no problems when coming from
a host in the US.

Alex.