Jan-Piet Mens wrote: > RFC 1034, section 3.6.2 specifies: "If a CNAME RR is present at a > node, no other data should be present" > > If other data (say an A RR) is present, BIND refuses (correctly) to > transfer the zone.
So the problem isn't with CNAME records, but people doing stupid things and so of course one solution is to prevent them from having CNAMEs, wouldn't it just make more sense to have triggers or something in the database prevent people from shooting themselves in the foot rather then reducing features? > I certainly have, in cases where users erroneously add a CNAME to a > record that already exists. BIND tries again and again, and then of > course, expires the zone. Perhaps I learnt from bind prior to using PDNS, but now that you explain it this way I remember upgrading between bind versions and transfers work with one version and not the new version. It was a very long time ago so details are a bit hazy. -- Best regards, Duane http://www.freeauth.org - Enterprise Two Factor Authentication http://www.nodedb.com - Think globally, network locally http://www.sydneywireless.com - Telecommunications Freedom http://e164.org - Because e164.arpa is a tax on VoIP "In the long run the pessimist may be proved right, but the optimist has a better time on the trip." _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
