Re: [Add] Zone ownership in DNS server discovery

This suggested behaviour seems to adversely impact the network-provided DNS
server capability to block access to malicious domains (e.g., malware,
phishing) and identification of exfiltration of data (e.g., TXT has been
typically misused by malware to exfiltrate data and to send C&C traffic).

-Tiru

On Fri, 11 Sep 2020 at 05:04, Tommy Jensen <Jensen.Thomas=
40microsoft.com@dmarc.ietf.org> wrote:

> 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
>
>   DNS over HTTPS: 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
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>