North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: root nameserver problems ?
-----BEGIN PGP SIGNED MESSAGE----- Yes - too hasty - I wasn't thinking right :-) j-m shouldn't have been on the list. We don't like reloading our nameservers prematurely, but when things like this happen, our NOC gets deluged with customer complaints very quickly :-( If we hadn't taken action, most of our customers using MCI nameservers for resolution purposes would still be unable to reach large portions of the internet. We really can't wait while these nameservers get fixed. Anyway, I'm glad there are already people working toward resolution of this problem. Thanks for the info ! - roy - >Roy, methinks you are a bit hasty here. j-m have never had tlds present. >And the other servers are being corrected as we "speak". But then, perhaps >you don't have a problem reloading your servers every couple hours or so... > >--bill >>COM. and NET. zone files were corrupted. >> >>a-g were affected by this corruption, h-i did not take the >>corrupted update (perhaps they're otherwise broken), and j-m >>do not serve the affected zones. >> >>a was finally corrected at 6:55am, and admins of b-g >>were asked to reload their zones. It appears that none >>of said admins have done so to date. >> >>J.ROOT-SERVERS.NET. 146428 A 188.8.131.52 >>K.ROOT-SERVERS.NET. 146428 A 184.108.40.206 >>L.ROOT-SERVERS.NET. 146428 A 220.127.116.11 >>M.ROOT-SERVERS.NET. 146428 A 18.104.22.168 >> >>should all be fine, so please remove them from your list. >> >>--jhawk >> -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBM84PaGx7n9NanyP9AQG+zwP/R8mo7C7vWlphf+gONOvgy8tWIJ40laps bupWG5KryzsC1z27KXAy1oSnSbgWt8WzzYre0w8qnCyw2ehpwNN/zQR99dLZSbYo xN/2724wRCZkTXDFeo3dMCFq+IwxpsVsOxwONLcPppcZXxh/uiRrryC7CjFGBn0b dyOtf/C/8rg= =h633 -----END PGP SIGNATURE-----