North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: root nameserver problems ?
> - From our vantage point, it looks like most of the root nameservers > have bad delegation data. Most of them return no delegation info > for what should be working domains: 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. > To enable our resolvers to work properly, we've had to tell them > to ignore the root nameservers which appear to have bad data. > On a Bind 4.X system, one can do this with the 'bogusns' configuration > directive: > > bogusns 128.9.0.107&255.255.255.255 192.33.4.12&255.255.255.255 > 128.8.10.90&255.255.255.255 192.203.230.10&255.255.255.255 > 192.5.5.241&255.255.255.255 192.112.36.4&255.255.255.255 > 198.41.0.10&255.255.255.255 193.0.14.129&255.255.255.255 > 198.32.64.12&255.255.255.255 198.32.65.12&255.255.255.255 J.ROOT-SERVERS.NET. 146428 A 198.41.0.10 K.ROOT-SERVERS.NET. 146428 A 193.0.14.129 L.ROOT-SERVERS.NET. 146428 A 198.32.64.12 M.ROOT-SERVERS.NET. 146428 A 198.32.65.12 should all be fine, so please remove them from your list. --jhawk
|