Re: [DNSOP] Redefining name canonicalization

2017-05-05 Thread Mark Andrews
In message <22dffab8-1459-4074-e519-3fdda0f3e...@redhat.com>, Florian Weimer wr ites: > On 04/21/2017 05:08 PM, Bob Harold wrote: > > > I can understand you wanting a "getfqdn" function to return the FQDN > (fully > > qualified domain name) without doing canonicalization. > > > > But just so we ar

Re: [DNSOP] Redefining name canonicalization

2017-05-05 Thread Florian Weimer
On 04/21/2017 05:08 PM, Bob Harold wrote: I can understand you wanting a "getfqdn" function to return the FQDN (fully qualified domain name) without doing canonicalization. But just so we are clear on the DNS terms, "access.redhat.com" and "access.redhat.com.edgekey.net" are "aliases" "e133.b.a

Re: [DNSOP] Redefining name canonicalization

2017-04-21 Thread Bob Harold
On Thu, Apr 13, 2017 at 5:29 AM, Florian Weimer wrote: > I would like to propose the restrict name canonicalization (as performed > by stub resolvers) to forming a fully-qualified domain name with the help > of the search list. > > With the current rules based on resolving CNAME chains, we end up