<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Michael,<div><br></div><div>I did some research and we do need to allow underscored in the first part of a NS record, as it refers to a domain</div><div><br></div><div><div>Let me quote the standard, RFC 2181, section 11, "Name syntax":</div><div><br></div><div>The DNS itself places only one restriction on the particular labels that can be used to identify resource records. That one restriction relates to the length of the label and the full name. [...] Implementations of the DNS protocols must not place any restrictions on the labels that can be used. In particular, DNS servers must not refuse to serve a zone because it contains labels that might not be acceptable to some DNS client programs.</div><div><br></div><div>See also the original DNS specification, RFC 1034, section 3.5 "Preferred name syntax" but read it carefully.</div><div><br></div><div>Domains with underscores are very common in the wild. Check _jabber._tcp.gmail.com or _sip._udp.apnic.net.</div><div><br></div><div>For host names (or for URLs, which include a host name), then this is different, the relevant standard is RFC 1123, section 2.1 "Host Names and Numbers" which limits host names to letters-digits-hyphen.</div><div><br></div><div>Best regards,</div><div><br></div><div>Taco</div><div><br><blockquote type="cite"><div>On 22 Aug 2024, at 13:16, Taco Scargo via Blueonyx <blueonyx@mail.blueonyx.it> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Colin,<div><br></div><div>In /var/named/chroot/var/named there should be a file of the specific domain with a .include extension</div><div>That’s where you would add a line, similar to (in case the domain is called <a href="http://example.com/">example.com</a>):</div><div><br></div><div><div>_acme-challenge.example.com. IN NS XXXXXX.</div></div><div><br></div><div>What XXX should be you should have received as well.</div><div>It is however quite uncommon to use NS records for verification, generally this is done with TXT records.</div><div>I would advise you to ask the customer for additional information.</div><div><br></div><div>Best regards,</div><div><br></div><div>Taco Scargo</div><div>taco@blueonyx.nl</div><div><br><div><br><blockquote type="cite"><div>On 22 Aug 2024, at 12:39, Colin Jack via Blueonyx <blueonyx@mail.blueonyx.it> wrote:</div><br class="Apple-interchange-newline"><div><div>Good morning.<br><br>Some guidance please.<br><br>We have a customer using a third party host for their website but we hold the DNS.<br>They have requested the following NS record to be added.<br><br>NS _acme-challenge domain.tld<br><br>This can't be done from the GUI so I will need to add to the include file but not certain on the format.<br>I don't want to mess it up!<br><br>Please can someone tell me what I need to do?<br><br>Many thanks<br><br>Colin<br><br><br>_______________________________________________<br>Blueonyx mailing list<br>Blueonyx@mail.blueonyx.it<br>http://mail.blueonyx.it/mailman/listinfo/blueonyx<br></div></div></blockquote></div><br></div></div>_______________________________________________<br>Blueonyx mailing list<br>Blueonyx@mail.blueonyx.it<br>http://mail.blueonyx.it/mailman/listinfo/blueonyx<br></div></blockquote></div><br></div></body></html>