On Sun, 2016-07-31 at 19:25 -0700, Dave Warren wrote:
Or, separate your resolver and authoritative roles, in which case this
won't be an issue. One should still monitor for zones for customers
who have departed, obviously, but it's not likely to cause any
operational issues.
On 01.08.16 10:37,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 2016-07-31 at 19:25 -0700, Dave Warren wrote:
> Or, separate your resolver and authoritative roles, in which case this
> won't be an issue. One should still monitor for zones for customers
> who have departed, obviously, but it's not likely t
On Sat, 2016-07-30 at 21:40 +0200, Matus UHLAR - fantomas wrote:
or simply wait till customers complain and tell them they should tell
you when tthey migrated their zones off.
On 31.07.16 18:00, Carl Byington wrote:
Which customers will complain?
funny that you have answered below.
Conside
On 2016-07-31 18:00, Carl Byington wrote:
Which customers will complain?
Consider the case where you have customer A and ex-customer B, and you
still have ex-customer B zones loaded in your master dns servers. The
rest of the world properly sees the (new) zone content for ex-customer
B.
But whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sat, 2016-07-30 at 21:40 +0200, Matus UHLAR - fantomas wrote:
> or simply wait till customers complain and tell them they should tell
> you when tthey migrated their zones off.
Which customers will complain?
Consider the case where you have cust
On 2016-07-29 08:21, Matus UHLAR - fantomas wrote:
On 28.07.16 12:13, Paul A wrote:
Now what is everyone using to make sure the zones in named.conf
are still
pointing to your NS servers? I have a lot of stale DNS zones I want to
remove.
separate authoritative and recursive servers.
bill for h
On 2016-07-29 08:21, Matus UHLAR - fantomas wrote:
On 28.07.16 12:13, Paul A wrote:
Now what is everyone using to make sure the zones in named.conf are
still
pointing to your NS servers? I have a lot of stale DNS zones I want to
remove.
separate authoritative and recursive servers.
bill for h
On 28.07.16 12:13, Paul A wrote:
Now what is everyone using to make sure the zones in named.conf are still
pointing to your NS servers? I have a lot of stale DNS zones I want to
remove.
separate authoritative and recursive servers.
bill for having zones in DNS.
or simply wait till customers com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2016-07-28 at 12:13 -0400, Paul A wrote:
> Now what is everyone using to make sure the zones in named.conf are
> still pointing to your NS servers? I have a lot of stale DNS zones I
> want to remove.
script a loop to "dig $zone ns @8.8.8.8 +
ng to your NS servers? I have a lot of stale DNS zones I want to
remove.
Thanks, Paul
-Original Message-
From: Tony Finch [mailto:d...@dotat.at]
Sent: Thursday, July 28, 2016 10:45 AM
To: Casey Deccio
Cc: Paul A ; bind-us...@isc.org
Subject: Re: getting not authoritative with som
Yes there is.
p
From: Casey Deccio [mailto:ca...@deccio.net]
Sent: Thursday, July 28, 2016 10:39 AM
To: Paul A
Cc: Tony Finch ; bind-us...@isc.org
Subject: Re: getting not authoritative with some notifies
On Thu, Jul 28, 2016 at 10:34 AM, Paul A mailto:ra...@meganet.net> >
Casey Deccio wrote:
> On Thu, Jul 28, 2016 at 10:34 AM, Paul A wrote:
>
> > Yes on both server and the slave and primary are listed on the NS RR.
> > I'm really at a loss here, the zone updates on the slave but I keep
> > getting that message.
>
> There's a difference between a server being liste
On Thu, Jul 28, 2016 at 10:34 AM, Paul A wrote:
> Yes on both server and the slave and primary are listed on the NS RR. I'm
> really at a loss here, the zone updates on the slave but I keep getting
> that
> message.
>
There's a difference between a server being listed in the NS RRset and a
serve
nd-us...@isc.org
Subject: Re: getting not authoritative with some notifies
Paul A wrote:
>
> named[7062]: client xx.xx.64.2#51056: received notify for zone 'xxx:
> not authoritative
>
> However some zones I don't get the message above some I do, I'm not
> usi
Paul A wrote:
>
> named[7062]: client xx.xx.64.2#51056: received notify for zone 'xxx: not
> authoritative
>
> However some zones I don't get the message above some I do, I'm not using
> views so I'm lost as to why this is happening.
Are you sure the zone is actually configured on the server tha
I have an issue I can't seem to figure out, when I make a zone change on the
master server it sends out notifies to the slave, the slave updates the zone
once it sees the notify but I get this in the logs.
named[7062]: client xx.xx.64.2#51056: received notify for zone 'xxx: not
authoritative
16 matches
Mail list logo
