On Wed, Dec 04, 2002 at 02:00:02PM -0500, Chimento, Douglas wrote: > > Could someone clarify the CNAMEANDOTHER hard error. > From what I read in the CHANGE file log and on mailing lists, > starting with verision 8.2 , CNAME and other data is a "hard error". > Also, is there a way of disabling this "hard" error ? If you actually serve such errors to the internet, your DNS won't work anyways - so there's no point in disabling it. > On a more personally note, > This CNAME error is a real pain and I am shocked that ISC would something so > drastic. > Besides, if my master server version 8.1.2 and my slaves are version 8.3.4 > .....the SLAVE STILL load the ZONE with the CNAME error. > So I don't see the point of a HARD error if slave load the zone ( possible > bug?) . > Why should admins be forced to deal with this error? Why should the rest of the internet be fed bad data? Trust me, you don't want this, it won't work like you think it will. Run a nameserver like tinydns that doesn't perform these checks, and enter the records. See how things work out. Basically you invalidate an entire zone/domain when you CNAME at the apex of it. If you have a CNAME for foo.example, then the SOA and NS records for foo.example will never work, will never be seen. The DNS protocol itself requires that you do not use CNAMEs at the apex of a zone, not the ISC. -- Nate Campi http://www.campin.net "The danger from computers is not that they will eventually get as smart as men, but we will meanwhile agree to meet them halfway." -Bernard Avishai "I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image." -Stephen Hawking -- Attached file included as plaintext by Ecartis -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE97lUFWpDEZMF673kRAtoNAJ9cOfECo+Gff4L54rQU9OGy5QTMiQCeJjnZ oYrCkZmTilG1MxJLuhqvvWI= =MZhe -----END PGP SIGNATURE-----