Browse all articles tagged with #dns.
A sending provider asks you to replace a DNS value, but nobody knows which team originally added it. Ownership becomes a delivery issue when changes sit unanswered.
Your provider asks for a DKIM host, and the DNS panel automatically appends the zone name. Pasting the full name into a field expecting only the label can publish the record somewhere unintended.
The new website loads after a nameserver change, but incoming mail stops. The new DNS zone may be missing records that were present in the previous one.
The website works behind Cloudflare, but the SMTP hostname stops accepting connections. Check whether the mail host was configured like an ordinary website host.
Some domains exist only for a website or another non-mail purpose. A null MX record is an explicit signal that the domain does not accept email; it is not a missing value that your importer should repair automatically.
You find a DMARC rollout guide that recommends increasing pct from 10 to 100. Before adopting it unchanged, check which version of the standard and which receiver behavior it assumes.
The DNS change is complete, yet a fresh email still carries the old selector. Before deleting more records, confirm which system actually sent that message.
You connected another sending tool and pasted its SPF instructions into a new TXT record. The old SPF record is still there. Both look valid when read separately, but that is the problem.
A short SPF record can still create a long DNS lookup chain. The visible line is only the beginning when it includes records maintained by other services.