It seems to me problematic to start with the statement that apex CNAME is
"deployed on the internet". Obviously it does occur, but it breaks things
when it does. Depending on various factors such as the order in which
responses are cached, the breakage is sometimes survivable, but you can't
put a
Mukund,
Thank you for reviving this conversation. I was just asked last week about the
status of this whole debate by someone who was seeking to set up “CNAME at
apex”-style records for a variety of domains, all of which would be pointed
over to links within various CDNs.
His challenge is
> On 14 Sep 2018, at 7:12 pm, Klaus Malorny wrote:
>
> On 14.09.18 00:55, Mark Andrews wrote:
>> I was testing TSIG with a well known key against TLD servers and got the
>> following response. Once you get past the bad class field (reported to the
>> operator) there were a
>> number of
this proposal appears to make more sense. if cname cannot be used until
everybody has upgraded, then some other ?name RR could be used instead,
on a similar time line, and would have no impact on those who never
upgraded.
___
DNSOP mailing list
Hi Petr
Apologies for the delayed reply.
On Tue, Jun 19, 2018 at 03:18:22PM +0200, Petr Špaček wrote:
> Hello dnsop,
>
> beware, material in this e-mail might cause your head to explode :-)
>
> This proposal is based on following observations:
> - It seems that DNS protocol police lost battle
