Interesting behavior with wildcard domains
Mathew Ian Eis
Mathew.Eis at nau.edu
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. bar.com, with what I’ll call a “second level” wildcard host, e.g. *.foo.bar.com A 10.10.10.5 in that zone. (as opposed to what might be considered the more usual wildcard host record of *.bar.com).
buz.foo.bar.com returns A 10.10.10.5 as expected.
However, a query for foo.bar.com 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,
Northern Arizona University
Information Technology Services
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users