Interesting behavior with wildcard domains

[Noel Butler]

On 24/02/2016 09:13, Mathew Ian Eis wrote:

> Hi BIND, 
> 
> 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, 
> 
> Mathew Eis 
> Northern Arizona University 
> Information Technology Services

It's expected, since its a *  "." foo... 
you are asking for anything thast dot foo, your not asking for foo 

-- 

 		If you have the urge to reply to all rather than reply to list, you
best first read  http://members.ausics.net/qwerty/

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20160224/03c0c804/attachment.html>