named-xfer will silently die when attempting to transfer the attached (odd, but perfectly rfc-legal) db file. If the CNAME reference at the bottom is removed, named-xfer will complete successfully. --------------------------------------------------------------------------------------------------------- @ IN SOA ns1.mfn.org. sysadmin.mfn.org. ( 980101 ; serial 10800 ; 3 hr refresh 3600 ; 1 hr retry 604800 ; 1 week expiration 86400 ) ; 1 day ttl ; ; Name Servers ; IN NS ns1 ns1.mfn.org. IN A 204.238.179.6 IN NS ns2 ns2.mfn.org. IN A 204.238.179.201 ; ;MX ; IN MX 10 greeves.mfn.org. ; ; host table ; localhost IN A 127.0.0.1 sebastion.mfn.org. IN A 204.238.179.1 greeves.mfn.org. IN A 204.238.179.35 ; ; aliases ; mfn.org. IN CNAME greeves.mfn.org. Fix: Workaround: If this type of reference is needed, then secondary dns services will break. Use 2 primary servers under these conditions. How-To-Repeat: use above file
>perfectly rfc-legal Not quite. RFC 1034 says: If a CNAME RR is present at a node, no other data should be present and since you have SOA and NS records for mfn.org, you may not have a CNAME for it. Bill
State Changed From-To: open->closed in any case this is an issue that should be brought to the BIND maintainers, not FreeBSD