<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><span></span></div><div dir="ltr"> The whole point of DNS Flag Day is that we don’t have any obligation to resolve domains running on broken DNS server. It have become “fix you sh^Htuff” instead of “fix our stuff” how it have been before.<br><br>Also it’s perfectly OK (on technical level) to not support EDNS, but in this particular case (<a href="http://p4.no">p4.no</a>) it’s the fact that the server returns FORMERR + OPT RR that’s causing the resolution failure as 6891 says:</div><div dir="ltr"><br></div><div dir="ltr">> <span style="background-color: rgba(255, 255, 255, 0);">Responders that choose not to implement the protocol extensions</span><pre class="newpage" style="margin-top: 0px; margin-bottom: 0px; break-before: page;"><font face="UICTFontTextStyleBody"><span style="white-space: normal; background-color: rgba(255, 255, 255, 0);"> defined in this document MUST respond with a return code (RCODE) of FORMERR to messages containing an OPT record in the additional
section and MUST NOT include an OPT record in the response.</span></font><span style="font-size: 1em; -webkit-text-size-adjust: auto;">
</span></pre><div><br></div>Cheers,<br>Ondrej<br><div id="AppleMailSignature" dir="ltr">--<div>Ondřej Surý <<a href="mailto:ondrej@sury.org">ondrej@sury.org</a>></div></div><div dir="ltr"><br>On 31 May 2019, at 18:01, <a href="mailto:sthaug@nethelp.no">sthaug@nethelp.no</a> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><blockquote type="cite"><span>During the period, the oldest encounter and one of the most critical was a 17 year old Authoritative Servers running Windows DNS. They have now fixed this, it took around 6 months for them. I believe they were not alone. </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Just because 99.9% looks OK in statistics, does not mean that it really work in real life scenarios. Businesses and Government organs still think that "DNS is old and easy service, we do not need to update". </span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Even if and when we reach out, there are instances that does not listen and still think it is our fault. </span><br></blockquote><span></span><br><span>And there are authors of DNS software out there who have no plans to</span><br><span>implement EDNS (not even minimalist correct answers) - read the mail</span><br><span>thread at</span><br><span></span><br><span> <a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users">https://mailman.powerdns.com/mailman/listinfo/pdns-users</a></span><br><span></span><br><span>and weep. No, it's not really about PowerDNS.</span><br><span></span><br><span>Steinar Haug, AS2116</span><br><span>_______________________________________________</span><br><span>dns-operations mailing list</span><br><span><a href="mailto:dns-operations@lists.dns-oarc.net">dns-operations@lists.dns-oarc.net</a></span><br><span><a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations">https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a></span><br><span>dns-operations mailing list</span><br><span><a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations">https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a></span><br></div></blockquote></div></body></html>