Find a CNAME Conflict in Supplied DNS Records
Admin ·
Review the records you plan to change together. A valid individual record can still conflict with another record at the same owner.
Validate five records, then add a conflicting CNAME
Choose Load example with DNS record text selected and press Validate DNS records. The result shows five parsed records and zero errors. Find the two different address families for shop.example.test. and the MX preference of 10 for example.test.
Append the example CNAME line below. Validate again. The six records now include a CNAME conflict at line 6. Review which data should belong at shop.example.test. and remove the unwanted record from the proposed set.
shop.example.test. 300 IN CNAME store.example.test.Open DNS Record ValidatorRFC 2181 DNS aliases and canonical names
Read the mail exchange and policy records separately
Confirm a normal MX line identifies a numeric preference and a named exchange. A sole MX record with data 0 . declares null MX. Add that line for example.test. while keeping the ordinary example MX and the tool reports a null MX conflict.
The TXT checks interpret visible SPF and DMARC syntax and flag competing policy records. A record set may contain only part of the DNS evidence used by a mail receiver.
RFC 7505 Null MXRFC 7208 SPF record syntaxRFC 9989 DMARC record interpretation
Keep the source of a saved DNS response
Choose Saved DNS JSON, then Load example and validate again. The report identifies the saved resolver label, timestamp and AD and CD flags. The example records one IPv6 address.
Open the JSON report to confirm the parsed address and the capture metadata agree with the source. The AD and CD flags are observations from the supplied response. Independent DNSSEC chain validation requires separate evidence.
Google DNS saved JSON response fieldsRFC 4035 DNSSEC protocol and flagsOpen DNS Record Validator
Common questions
Can an empty saved MX answer establish which server accepts mail?
It records no MX in the supplied answer. Check response status and coverage. A published null MX has the explicit value 0 .
Why does the validator keep the capture timestamp with the result?
DNS answers can change. The timestamp identifies the recorded observation and helps you compare it with a later capture.