Removing an NS server
johnmill at brandeis.edu
Tue Aug 7 21:01:06 UTC 2018
Hal, we've done this before - it's not particularly hard, just takes a
bit for everyone to pick up the new set of NS records. You just make
the change upstream and also remove the NS records that reference the
system. It's kind of weird: during the interim, you'll have a running
nameserver that doesn't return itself in its NS records. If the same
set of servers also serves your reverse zones, don't forget to update
ARIN as well as Educause.
Educause sets their upstream TTLs to two days (ARIN's 1 day), but
people shouldn't be caching the referral, only your actual NS records.
If you're at all concerned, you can always set a low TTL ahead of time
on your NS records, so everyone will pull the updated records
relatively quickly once you make your changes.
On Tue, Aug 7, 2018 at 4:46 PM, King, Harold Clyde (Hal) <hck at utk.edu> wrote:
> I don't think I made my point. I need to pull/remove a DNS nameserver from my set of nameservers.
> My plan was to put the reference to it from our domain name provider. Then pull it from the list of NS records. I am not changing my SOA record. Just the nameserver. Did I make a mistake? Did you mean pull the NS reord for that server, then pull it from the name provider. I'll still have 4 servers running the SOA, and I don't plan to stop the old nameserver until well after a week of running.
> Hal King - hck at utk.edu
> Systems Administrator
> Office of Information Technology
> Shared Systems Services
More information about the bind-users