On 15/01/2025 10:47, Emmanuel Fusté wrote:
If so, does the ISC ship a db.local with a wildcard - eg.
--- cut here ---
@ IN NS localhost.
@ IN A 127.0.0.1
@ IN AAAA ::1
* IN A 127.0.0.1
IN AAAA ::1
--- cut here ---
to answer for any .localhost name?
Don't please. See RFC6761
From RFC 6761:
6.3. Domain Name Reservation Considerations for "localhost."
The domain "localhost." *and any names falling within ".localhost."*
are special in the following ways:
...
4. Caching DNS servers SHOULD recognize localhost names as special
and SHOULD NOT attempt to look up NS records for them, or
otherwise query authoritative DNS servers in an attempt to
resolve localhost names. Instead, caching DNS servers SHOULD,
for all such address queries, generate an immediate positive
response giving the IP loopback address, and for all other query
types, generate an immediate negative response. This is to
avoid
unnecessary load on the root name servers and other name
servers.
5. Authoritative DNS servers SHOULD recognize localhost names as
special and handle them as described above for caching DNS
servers.
To me this seems like a pretty clear endorsement for inclusion of the
wildcard entry "*.localhost." in db.local?
Nick.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
