B
Ben
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I'm seeing a lot of "lame server" messages from my name server
when trying to resolve mail.python.org and neither my name server
(devious.adversary.org) nor those of my upstream
(yarrina.connect.com.au & warrane.connect.com.au). In fact, one of my
upstream's caches (yalumba.connect.com.au) is locating what appears to
be invalid nameservers for python.org.
Yalumba believes python.org's nameservers are ns53.worldnic.com &
ns54.worldnic.com. While tracking back from UltraDNS points to
ns.xs4all.nl & ns2.xs4all.nl.
So does anyone know if there are currently any registration or
delegation issues with python.org or if they are seeing similar things
elsewhere?
Regards,
Ben
P.S. I tried to send this to the list a little while ago, but of
course my system is having trouble reaching it.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBP+OnHzcaxb+gSuMTEQK9nQCglFtxnRqMa1DDnUcNy54Q8xru58cAn2uw
ermzA282kdJyBQF9Qi9H+zBS
=rGRG
-----END PGP SIGNATURE-----
Hash: SHA1
Hi all,
I'm seeing a lot of "lame server" messages from my name server
when trying to resolve mail.python.org and neither my name server
(devious.adversary.org) nor those of my upstream
(yarrina.connect.com.au & warrane.connect.com.au). In fact, one of my
upstream's caches (yalumba.connect.com.au) is locating what appears to
be invalid nameservers for python.org.
Yalumba believes python.org's nameservers are ns53.worldnic.com &
ns54.worldnic.com. While tracking back from UltraDNS points to
ns.xs4all.nl & ns2.xs4all.nl.
So does anyone know if there are currently any registration or
delegation issues with python.org or if they are seeing similar things
elsewhere?
Regards,
Ben
P.S. I tried to send this to the list a little while ago, but of
course my system is having trouble reaching it.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBP+OnHzcaxb+gSuMTEQK9nQCglFtxnRqMa1DDnUcNy54Q8xru58cAn2uw
ermzA282kdJyBQF9Qi9H+zBS
=rGRG
-----END PGP SIGNATURE-----