Interesting behavior with wildcard domains

Mathew Ian Eis Mathew.Eis at
Tue Feb 23 23:13:39 UTC 2016


I’ve encountered (quite by accident) an interesting behavior in BIND with wildcard domains:

The relevant configuration is a zone; e.g., with what I’ll call a “second level” wildcard host, e.g. * A in that zone. (as opposed to what might be considered the more usual wildcard host record of * returns A as expected.

However, a query for returns NOERR with zero results, when I would expect a NXDOMAIN.

Anyone know if the NOERR with zero results is the expected / correct behavior?

Thanks in advance,

Mathew Eis
Northern Arizona University
Information Technology Services

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list