[nsd-users] nsd do not resolve .in domains

[Matthijs Mekking]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm sorry, I got confused with the source of synthesis, that is the
wildcard should *immediately descend* from the closest in closer.

- - In that case (assuming there is an entry with .in), if I query for
"whatever.domain.in." (type A, class IN), I need to have

	*.in. IN A 1.2.3.4

in my zonefile.

- - If that assumption is wrong, then indeed the RR

	*. IN A 1.2.3.4

should match it.

The complete contents of the root.zone file would help to see what's
really going on.


Best regards,

Matthijs

W.C.A. Wijngaards wrote:
> Hi Roy,
> 
> Well, if there is another entry with .in, then the "*." wildcard does
> not cover .in any longer.
> 
> Short statements can be hard to understand. :-)
> 
> Best regards,
>    Wouter
> 
> On 04/22/2010 04:28 PM, Roy Arends wrote:
>>> (note that wildcards only go one level deep).
>> They do?
_______________________________________________
nsd-users mailing list
nsd-users at NLnetLabs.nl
http://open.nlnetlabs.nl/mailman/listinfo/nsd-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJL0VLeAAoJEA8yVCPsQCW5+R0IAJxXv76zhAhNHQI7PIG617qr
TmbGtZRVtG/sLlfjDjsVn8XQwnuvoD/7QZelNxQgSGhY28Xv2IqlSbtlgv6wTMcM
E+M/xntw35X/bHUVosrADuE7a7xCBhP5BjyBlsHqR3fvDOehBoXnjtT+EAcdbOWG
rOxdJe9xLET0P/Nu00500oR+EFKbzs4e2CVbywUnC2CCWDASzggLvIhJ5NeppY6f
xMJ8ortKqp9ycvip6AD21hppN/mFQS/0VAyethSeaUX5p2I4WQdu5Se+HoNebzUF
na3VKbId6RyVdHIsJyPFBq+i9B0jlnLNAxp/m41rJTnjw9CzixFm1yuCNqH2UII=
=z1/a
-----END PGP SIGNATURE-----