Bind 9: Wildcard-Bug ?

Florian Sager sager at agitos.de
Sat Aug 30 16:49:02 UTC 2008


Hi,

I am using Bind 9.3.4 with RRs like

$ORIGIN 000baea3d8f9b6c98eb33e73092e5342.al.domain.tld.
*                       TXT     "data"

Requests and return values:
1) dig TXT test.000baea3d8f9b6c98eb33e73092e5342.al.domain.tld --> data = OK
2) dig TXT abc.test.000baea3d8f9b6c98eb33e73092e5342.al.domain.tld --> 
data = OK
3) dig TXT test.test.000baea3d8f9b6c98eb33e73092e5342.al.domain.tld --> 
NXDOMAIN ???

Is there any reason why equal <sub>.<sub> requests [see (3)] result in a 
NXDOMAIN ?

Additional information: if the RR "test.test" is explicitly contained in 
the zone the 3rd request correctly returns "data".
Therefore I assume a wildcard bug in Bind 9 ? (I didn't try it with an 
earlier version).

Thanks,
Florian



More information about the bind-users mailing list