[nsd-users] CNAME for domain.tld failing

[W.C.A. Wijngaards]

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

Hi Bobb,

On 01/07/2011 03:18 AM, Bobb Voigt wrote:
> Is there any way to tell nsd that i dont care about section 3.6.2 of
> the RFC and to do what i say?
>
> while technically wrong, it's worked as intended on many of my domains...
> and it really simplifies moving a node from one DC to another...

What you want is indeed not allowed, specifically this one line in the
zonefile:
@	IN CNAME bla.bla.bla
You could comment that one line and keep the other CNAMEs below the zone
apex.

If you really want NSD to ignore section 3.6.2, use the attached patch.
 I have not tested the patch, but in code it looks like it may do what
you want (return positive answers and otherwise the CNAME).

There is no support for this patch :-)

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0m2RAACgkQkDLqNwOhpPhNXgCfZPzk7fNK7DPoXq5ydVbKLU5+
VlsAn1jvr3ZkA3VVXFFCX0LB7q3DbHdq
=h982
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch.ignore_1034_362_CNAME
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20110107/5326ad7e/attachment.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch.ignore_1034_362_CNAME.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20110107/5326ad7e/attachment.bin>