On Wed, Aug 8, 2018 at 9:10 AM, Bob Harold wrote:
>
> On Tue, Aug 7, 2018 at 5:01 PM John Miller wrote:
>>
>> 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
On 07.08.18 20:46, King, Harold Clyde (Hal) 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.
Yes, to be more precise, you must pull the name out of all domains delegated
ity of Tennessee
103C5 Kingston Pike Building
2309 Kingston Pk. Knoxville, TN 37996
Phone : 974-1599
Helpdesk 24/7 : 974-9900
From: Bob Harold
Date: Wednesday, August 8, 2018 at 09:10
To: John Miller , Hal King
Cc: Bind Users
Subject: Re: Removing an NS server
On Tue, Aug 7, 2018 at 5:01 PM John
On Tue, Aug 7, 2018 at 5:01 PM John Miller wrote:
> 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:
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 d
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 m
6 matches
Mail list logo
