Slow IN-ADDR.ARPA responses

I'm seeing surprisingly slow responses from some of the IN-ADDR
servers, like 300ms or more. Are they being attacked by script
kiddies of something?

R's,
John

Hi John

I checked the traffic graphs for the server we operate
(a.in-addr-servers.arpa) and it has normal traffic loads. Have not heard
of any report of issues with the other operators.

Regards,
Mark

I checked the traffic graphs for the server we operate
(a.in-addr-servers.arpa) and it has normal traffic loads. Have not heard
of any report of issues with the other operators.

Actually, the A server is the only one that's responding quickly,
viewed from my DSL line hanging off gblx:

A 26ms
B 83ms
C 308ms
D 136ms
E 248ms
F 96ms

An acquaintance at LinkedIn tells me that they're seeing the same issue.

Doing a traceroute to the C server, it looks pretty snappy as far as
London, then slow as soon as it's in Afrinic's network. I think it's
usually faster than that. For the E server, the link between HE in
California and Australia seems slow.

R's,
John

Hi John

I have seen similar cases in past with root servers itself. Usually
problems are that local anycasted node here goes down and thus traffic is
redirected to other nearest server in Europe causing high latency. Can you
share traceroute result of a good Vs bad node say A Vs C. Can you see both
coming from within your country?

We operate B.* and we don't see anything unusual in our locations.

thanks

Mehmet

We operate B.* and we don't see anything unusual in our locations.

Seems to have been routing problems with C. The B server looks fine
from here, too. Thanks, all.

R's,
John