On Jun 22, 2014, at 2:14 AM, John Levine jo...@taugh.com wrote:
Reactions have been, um, mixed. Some folk say it;s a no-brainer,
others seriously dislike the idea.
As I understand it, this changes DNS caches so that for the root zone
its behavior is somewhere between a cache and a secondary
As I understand it, this changes DNS caches so that for the root zone
its behavior is somewhere between a cache and a secondary master.
The cache remains precisely a cache.
I understand that it's still a cache in the DNS hierarchy, but in
operation, it's much more like a secondary master.
On 22 Jun 2014, at 11:54, John Levine jo...@taugh.com wrote:
As I understand it, this changes DNS caches so that for the root zone
its behavior is somewhere between a cache and a secondary master.
The cache remains precisely a cache.
I understand that it's still a cache in the DNS
I understand that it's still a cache in the DNS hierarchy, but in
operation, it's much more like a secondary master. Like a secondary,
it bulk fetches the zone, answers all queries about that zone from its
own copy, and uses the SOA times to decide when to fetch again.
There are some
In message alpine.bsf.2.11.1406221459160.94...@joyce.lan, John R Levine
writes:
I understand that it's still a cache in the DNS hierarchy, but in
operation, it's much more like a secondary master. Like a secondary,
it bulk fetches the zone, answers all queries about that zone from its
On 22 Jun 2014, at 18:41, Joe Abley jab...@hopcount.ca wrote:
On 22 Jun 2014, at 11:54, John Levine jo...@taugh.com wrote:
As I understand it, this changes DNS caches so that for the root zone
its behavior is somewhere between a cache and a secondary master.
The cache remains
