CNAME Misconfiguration? Discrepancy between Bind 8.2.3 and Bind 8.2.2?

digest at cihost.com digest at cihost.com
Wed Feb 14 06:13:15 UTC 2001


After upgrading to BIND 8.2.3, every single record of mine based entirely on
CNAMES appears to not work now, can someone explain to me why they wouldn't
work? They worked fine in 8.2.2-P*, but aren't working in 8.2.3. Any
suggestions?




This is the master zone file:
*******************************************
$ORIGIN net.
mytestdomain   IN   SOA  ns.nsdomain.net. hostmaster.nsdomain.net. (
                2000051920 86400 7200 3600000 28800 )
                IN      NS      ns.nsdomain.net.
                IN      NS      ns2.nsdomain.net.
                IN      CNAME   otherdomain.com.
$ORIGIN mytestdomain.net.
mail            IN      CNAME   mail.otherdomain.com.
ftp             IN      CNAME   ftp.otherdomain.com.
www             IN      CNAME   www.otherdomain.com.
*******************************************





And here is the section from named.conf:
*******************************************
zone "mytestdomain.net" {
        type master;
        file "mytestdomain.net.b";
};
*******************************************

These are the errors:
*******************************************
Feb 13 19:26:36 vns2 named[761]: mytestdomain.net has CNAME and other data
(invalid)
Feb 13 19:26:36 vns2 named[761]: mytestdomain.net.b:4:ourcourts.net: CNAME
and OTHER data error
Feb 13 19:26:36 vns2 named[761]: mytestdomain.net has CNAME and other data
(invalid)
Feb 13 19:26:36 vns2 named[761]: mytestdomain.net.b:3:ourcourts.net: CNAME
and OTHER data error
Feb 13 19:26:36 vns2 named[761]: master zone "mytestdomain.net" (IN)
rejected due to errors (serial 2000051920)
*******************************************

What would make this invalid?

Thanks,
Digest



More information about the bind-users mailing list