cnames...

Cricket Liu Cricket at VeriSign.com
Mon Feb 5 15:49:06 UTC 2001


>> The solution is to add an
>> address record pointing your zone's domain name to the the address of
>> your web server.
>
> In this case there is no simple "address" at the root, the domain name
has]
> to point to a BGP4 thing run by Akamai that changes all the time depending
> on where you are.
>
> I'm pretty sure that the fact that the CNAME record conflicts with SOA/NS
> records is simply an oversight in RFC1034/3.6.2.  Logically, no record
type
> should "conflict" with the SOA.  The SOA isn't a normal record type, it's
a
> definition of the zone's maintenance parameters.  Also, the fact that all
> resolvers on all platforms work with this information is evidence that the
RFC
> may have been severely flawed.

Well, that's an interesting theory.

> So far, my solution has been to patch BIND 8.2.3 - which works quite well.

Okay, it's your zone.

cricket



More information about the bind-users mailing list