OMG Thank you! I had just cut and paste what the customer provided me! It works
when I correct the typo.
From: Brian Candler
Date: Monday, December 5, 2022 at 10:00 AM
To: Tony Annese , 'pdns-users@mailman.powerdns.com'
Subject: Re: [Pdns-users] CNAME Resoluion
On 05/12/2022 17:58, Tony
On 05/12/2022 17:58, Tony Annese via Pdns-users wrote:
[Error] Record 'enterpriseenrollment.icdf3.org IN CNAME
enterpriseenrollment.manage.microsoft.com' in zone 'icfd3.org' is
out-of-zone.
Read the error carefully.
Hint: icdf3.org != icfd3.org
:-)
So PDNS is reporting these CNAMEs as errors/being out of zone
root@nspower:~# pdnsutil check-zone icfd3.org
Dec 05 09:42:24 [bindbackend] Done parsing domains, 0 rejected, 0 new, 0 removed
[Error] Record 'enterpriseenrollment.icdf3.org IN CNAME
enterpriseenrollment.manage.microsoft.com' in zone
Hello,
what does "pdnsutil check-zone icfd3.org" on the Master say?
best regards,
Markus
Von: Pdns-users Im Auftrag von Tony
Annese via Pdns-users
Gesendet: Montag, 5. Dezember 2022 12:20
An: pdns-users@mailman.powerdns.com
Betreff: Re: [Pdns-users] CNAME Resoluion
Externe E-Mail
Vorsicht!
Those were wildcard entries for the whole domain icfd3.org.
I’ve removed those and get the same behavior. It also doesn’t explain why
barracuda058130353572.icfd3.org does resolve.
PDNS is my master server and ns.whidbey.net/ns.whidbey.com are my slaves. I
just added testing.icfd3.org and it
