ns5.linode.com
However, the PTR record for the associated IP address is "li141-10.members.linode.com". I'm assuming ns5 is in London; does the PTR record suggest that it's a temporary thing, or is it going to stick around (i.e., is it safe to use as one of our domain's nameservers)? And can the PTR record be fixed in that case, so it doesn't look like someone's hijacked it?
8 Replies
Besides, they would not have put it in everybody's NS records if that were not the case.
Thanks for the heads-up!
@glg:
Is it suggested that we go add this to the namservers at our registrars?
Fire away – it's just as ready as ns1 through ns4 are.
@BarkerJr:
Is there some way that everyone could be notified about the new server? That would take some of the load off the the other four, and people wouldn't freak out about the log entries denying it.
From your description, I think you mean those with a slave domain pointed at their own master instead of everyone.
For those with master domains in the Linode Manager, ns5.linode.com just appeared in the zone with no alteration required.
In the case you are asking about, if your master does not send notifies to a nameserver (including ns5) it will not be asked for your zone file by said nameserver – they all operate independently of each other for various reasons. With that in mind, there should not be any log entries denying ns5 unless you specifically configure your authoritative daemon to talk to it.
It gets updated each refresh seconds but I would prefer to use notifies. ns1-4 gets updated few seconds after sending new notifies.
