<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 10 March 2018 at 04:08, Matus UHLAR - fantomas <span dir="ltr"><<a href="mailto:uhlar@fantomas.sk" target="_blank">uhlar@fantomas.sk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cathy Almond <<a href="mailto:cathya@isc.org" target="_blank">cathya@isc.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The <a href="http://rs.dns-oarc.net" rel="noreferrer" target="_blank">rs.dns-oarc.net</a> zone is broken because it returns a CNAME for<br>
queries at the apex.<br>
</blockquote></blockquote>
<br></span><span class="">
On 09.03.18 15:23, Tony Finch wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I just got a problem report from a user who has a few personal domains<br>
with CNAME at apex that used to work (or at least appeared to work) but<br>
no longer do.<br>
<br>
I've said that the domains are misconfigured, but since this is a<br>
relatively widespread misconfiguration, I think it's likely to cause<br>
more complaints. Tiresome.<br>
</blockquote>
<br></span>
it's the very common result of misconfiguration that something sometimes<br>
does not work, while sometimes it does.<br></blockquote><div><br></div><div>Apex CHAMEs, in particular, have nondeterministic failure modes. In that, each resolver deals differently with this misconfiguration, since by definition there is no correct way to deal with it. Some resolvers find a way to gloss over the problem, and others fail hard making the domain name and everything below it unresolvable for the TTL of either the apex NS set or the TTL of the CNAME itself, depending on which way it breaks. </div><div><br></div><div>Best to just stop doing that so that whether the domain works doesn't depend on which resolver you're trying to use.</div><div><br></div><div><br></div></div></div></div>