10 Feb
2012
10 Feb
'12
7:04 p.m.
Hi Keith,
On Fri, Feb 10, 2012 at 06:34:33PM +0000, Keith Williams wrote:
I got a warning email saying that c.authns.bitfolk.com
was suffering s
critical error, then very soon afterwards an email saying it was recovered.
Sorry about that. I made a mistake and corrected it about a minute
later. It was enough for some people to get some alerts.
I did a quick check with intodns.com and all was well
except this
Same GlueLooks like the A records (the GLUE) got from the parent zone
check are different than the ones got from your nameservers. You have to
make sure your parent server has the same NS records for your zone as you
do.I detected some problems as follows:
For *c.authns.bitfolk.com* the parent reported: *['209.237.247.198']* and
your nameservers reported: *['173.255.227.192']*
I'm just writing an email about this but basically there's nothing
to worry about. c.authns.bitfolk.com has been renumbered and for a
short time, the root nameservers may have the old IP address (which
still works anyway).
Everytime I refresh it reports slightly differently
with server c always
reported as wrong sometimes all three
..but I can't see how or why all three should be reported that way
as nothing has changed with the other two.
I always tend to use http://squish.net :
http://dns.squish.net/traverses/086a4b6aaef7e9dddfecbb55fbec489e/detail
and that seems happy.
--
http://bitfolk.com/ -- No-nonsense VPS hosting