Re: [Add] Zone ownership in DNS server discovery

["Vinny Parla (vparla)" <[e-mail]>]

Thanks for the clarification.

I concur that this divergent behavior exists today with classic DNS.  Look
no further than TTL caching behavior of Outlook or Browsers.

 

I don't view this as a good thing but clearly understand the guidance being
given below.

 

-Vinny

 

From: Add <[e-mail]> On Behalf Of Tommy Jensen
Sent: Thursday, September 10, 2020 7:34 PM
To: Vinny Parla (vparla) <vparla=[e-mail]>
Cc: Jim Reid <[e-mail]>; ADD Mailing list <[e-mail]>
Subject: Re: [Add] Zone ownership in DNS server discovery

 

Hey Vinny,

 

Yes, but I'd say that's not a hypothetical statement and is already true
today. A DNS client could implement a full recursive if they wanted to for
example and cache authoritative servers they discover, an extreme example of
"bypassing" a need for a recursive. 

 

I'm just suggesting the decision of what server to query for a given name is
up to individual implementors, and domains providing authoritative
information about designated DNS servers would make that easier than having
to be a full recursive (since you can slowly bootstrap these designations).

 

Thanks,

Tommy

================================================

The latest in Windows Internet Protocols:

  Native gRPC support:  <https://aka.ms/grpcblogpost>
https://aka.ms/grpcblogpost 

  DNS over HTTPS:  <https://aka.ms/dohblogpost> https://aka.ms/dohblogpost 

 

 

  _____  

From: Vinny Parla (vparla)
Sent: Thursday, September 10, 2020 4:18 PM
To: Tommy Jensen
Cc: ADD Mailing list; Jim Reid
Subject: [EXTERNAL] RE: Zone ownership in DNS server discovery 

 

Hi,

 

So if I understand the statement below, it is entirely up to an algorithm of
the implementor, which could differ from endpoint to endpoint or browser to
browse, to choose either to use the authoritative vs the recursive resolver.

 

Did I understand this correctly?

 

Thanks,

 

-Vinny