You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Create an A Record with some name
2. Create an CNAME Record with the same name
3. Record gets created successfully and this breaks AXFR requests from Bind to
PDNS
What is the expected output? What do you see instead?
An Error message telling a record with this name already exists with a
different type
This affects multiple different record types which are not allowed in
combination, this can be a really big issue if not detected in time (this will
break the complete zone if there is a bind slave). Unfortunately only a few
interfaces for pdns support checks for this, so this would be a really great
feature/fix.
Original issue reported on code.google.com by [email protected] on 27 Nov 2012 at 8:25
The text was updated successfully, but these errors were encountered:
Yes this has to be implemented. But i first need to get a full list of record
types that are not allowed in combination...
For example A records or NS records are allowed (for the sake of load balancing
via DNS)
Original comment by timo.witte on 2 Mar 2013 at 2:12
RFC 1912 (http://www.ietf.org/rfc/rfc1912.txt) states that "A CNAME record is
not allowed to coexist with any other data".
According to that same RFC, the only exception are PTR records "if you want to
implement classless in-addr delegation".
Original issue reported on code.google.com by
[email protected]
on 27 Nov 2012 at 8:25The text was updated successfully, but these errors were encountered: