Christian Kuehn wrote:
we found that PDNS accept a CNAME for the domain (@) and announce this to all
other resolvers and dns-servers.
The problem is now that BIND did not accept this (error: CNAME ON TOP OF
DOMAIN), and its the same problem with CNAME AND OTHER DATA (CNAME plus NS/SOA).
Bind doesnt accept this zone as a slave-zone.
Any idea how to solve it ??
A man goes to the doctor, says "Doctor, it hurts when I do this" -
doctor tells him "then don't do that". In short, go with the doctor's
advice. Just don't do it. While there should probably be some kind of
check in PowerDNS to prevent it, it's broken behavior (since a CNAME
can't coexist with any other record - SOA and NS records included).
--
Derrik Pates
[EMAIL PROTECTED]
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
