[This has no operational consequences, it is just idle curiosity.]
A server receives a few packets/second coming from several IP
addresses and querying ./NS (like in priming, or may be in some
reflection attacks). The server was never a root server, of course.
What is interesting is that all
--- Begin Message ---
So a test stealth server was setup with an existing zone. It had a lower
SOA serial than the running one, yet the master accepted a zone transfer
and started using the outdated zone.
The only thing is AXFRs were allowed but not query, so I see the notify
from
the test
Sue Steffen:-
>We have created numerous subzones and delegated them to AWS private hosted
>zones for our move to the cloud efforts. This has resulted in a sprawl
>of subzones. Does anyone else have thoughts on how to manage the number of
>zones? How do you maintain currency on them like
Hi Thomas,
On 5/23/22 15:48, Thomas, Matthew wrote:
In the 2012 round of new gTLDs, DNS data collected at the root server system
via DNS-OARC’s DITL collection was used to assess name collision visibility.
The use of DITL data for name collision assessment purposes has growing
limitations in
