Alexander Clouter wrote:
Sometimes hostmaster@ should receive some pain for misconfiguration: ... alex@chipmunk:~$ host -t NS freeradius.org ns3.freeradius.org ;; connection timed out; no servers could be reached
That's been down for a while...
alex@chipmunk:~$ host -t NS freeradius.org ns6.freeradius.org ;; connection timed out; no servers could be reached
That should not have been down. It got rebooted, and powerdns didn't come back up.
alex@chipmunk:~$ host -t NS freeradius.org ns5.freeradius.org Using domain server: Name: ns5.freeradius.org Address: 88.191.76.128#53
That's the one I monitor continuously.
For some reason freeradius has three NS servers being spat out by the .org TLD authority boxen, you ask the *only* responding authority server for freeradius.org and it comes back that there are only two authoritative servers for the zone. :)
Yes, well...
If this is a recent breakage, it's possible either ns3 or ns6 gave back something interesting (NXDOMAIN for example) which have be cached by your resolver just before it completely went down.
Either way, freeradius.org probably could do with more than one authoritive DNS server :)
It should have two. Alan DeKok.