<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p>I hope that the following conforms to the content expected of
this list.</p>
<p><br>
</p>
<p>I stumbled on some <i>name servers</i> (a branch of a ccTLD,
performing a public good service, as far as I know) which are
giving a FORMat ERRor (FORMERR) to default <i>dig</i> queries
from the command line as described in the referenced webpage, see
[1] below. The workaround of +nocookie described in the blog
allows for a successful query response. <i>Nslookup</i> queries
work fine.<br>
</p>
<p><br>
</p>
<p>I should mention that I have no administrative authority of the
name servers showing this condition. I'm just noticed the
behaviour whilst checking on a DNS hosting migration for a client
of the name servers exhibiting the behaviour.<br>
</p>
<p><br>
</p>
<p>Would someone be able to advise me on:</p>
<ol>
<li>How bad it may be for an authoritative or delegating name
server to be exhibiting this behaviour? <br>
</li>
<li>Does this potentially cause a resolution outage, or would a
BIND server adjust and re-query in order to obtain a usable
result? <br>
</li>
<li>Is the BIND server non-compliant, or the likely Microsoft DNS
non-compliant, to an RFC?</li>
<li>How would I explain such an issue to a name server operator
who I do not know?<br>
</li>
</ol>
<p><br>
</p>
<p>I appreciate any guidance provided. I apologies in advance if I
violated any list policy. Thanks for any assistance.<br>
</p>
<p><br>
</p>
<p><font size="+2"><b>REFERENCE</b></font></p>
<blockquote>
<p>[1] FORMERR from Microsoft DNS Server for DIG. Posted January
20, 2017 at 11:18 PM MST by Kevin Locke <<a
moz-do-not-send="true"
href="https://kevinlocke.name/bits/2017/01/20/formerr-from-microsoft-dns-server-for-dig">https://kevinlocke.name/bits/2017/01/20/formerr-from-microsoft-dns-server-for-dig</a>>.<br>
</p>
</blockquote>
<p><br>
</p>
<p>Regards,</p>
<p><br>
</p>
<p>Jason Hynds.<br>
</p>
</body>
</html>