That I get. That's why I deleted and applied. Turns out the issue was in the PowerDNS Admin interface. I was able to fix via PHPIPAM
*Larry G. Wapnitsky* *E: la...@wapnitsky.com* *Web: Larry.Wapnitsky.com <http://larry.wapnitsky.com/>Twitter: @LGWapnitsky* On Fri, Mar 26, 2021 at 4:43 PM Brian Candler <b.cand...@pobox.com> wrote: > On 26/03/2021 20:29, Larry Wapnitsky via Pdns-users wrote: > > I'm looking to replace A records with CNAMES, and have been able to do so > seamlessly on one of my domains, but another keeps giving me errors relating > to RRSET conflict ( IN CNAME: Conflicts with pre-existing RRset). > > I've deleted the necessary A records, yet keep running into the same issue. > > At any given point in the tree, you can't have both a CNAME and any other > resource record. > > foo.bar.baz. IN MX mail.example.com. > foo.bar.baz. IN CNAME abc.def.ghi. ; NOT ALLOWED because it > conflicts with the MX record > > This is most commonly a problem at the apex of a zone, where there are > already SOA and NS records. > > The 'ALIAS' pseudo-RR exists to solve this problem. It's not served > directly, but when an incoming A/AAAA request arrives, the right-hand side > of the ALIAS record is resolved (externally), and then the result of that > is returned as the result of the original query. > > See: https://doc.powerdns.com/authoritative/guides/alias.html > > >
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
