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
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.
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
-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
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
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
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
-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
Tony,
the zones that are giving me the not auth error are indeed off cache, as I
see the RA flag and the AA is missing. I never really thought this was
happening because I have all zones configure the same way and some are not
getting the not auth error and have the aa flag present. I was
10 matches
Mail list logo
