<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 15/01/2025 10:47, Emmanuel Fusté
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0973c4d6-71b6-482e-beaf-99def917592e@gmail.com">
<blockquote type="cite" style="color: #007cff;">If so, does the
ISC ship a db.local with a wildcard - eg.
<br>
--- cut here ---
<br>
@ IN NS localhost.
<br>
@ IN A 127.0.0.1
<br>
@ IN AAAA ::1
<br>
<br>
* IN A 127.0.0.1
<br>
IN AAAA ::1
<br>
--- cut here ---
<br>
<br>
to answer for any .localhost name?
<br>
</blockquote>
Don't please. See RFC6761
</blockquote>
<p>From RFC 6761:<br>
</p>
<blockquote>
<p>6.3. Domain Name Reservation Considerations for "localhost."<br>
<br>
The domain "localhost." <b>and any names falling within
".localhost."</b><br>
are special in the following ways:<br>
...<br>
4. Caching DNS servers SHOULD recognize localhost names as
special<br>
and SHOULD NOT attempt to look up NS records for them, or<br>
otherwise query authoritative DNS servers in an attempt
to<br>
resolve localhost names. Instead, caching DNS servers
SHOULD,<br>
for all such address queries, generate an immediate
positive<br>
response giving the IP loopback address, and for all
other query<br>
types, generate an immediate negative response. This is
to avoid<br>
unnecessary load on the root name servers and other name
servers.<br>
<br>
5. Authoritative DNS servers SHOULD recognize localhost
names as<br>
special and handle them as described above for caching
DNS<br>
servers.<br>
</p>
</blockquote>
<p>To me this seems like a pretty clear endorsement for inclusion of
the wildcard entry "*.localhost." in db.local?<br>
</p>
<p>Nick.<br>
</p>
</body>
</html>