- Home
- Domain, DNS and IP
- DNS Lookup
DNS Lookup
Read a domain’s entire DNS configuration, from web routing to email.
Direct queries to the DNS servers authoritative for the domain, without passing through an intermediate cache. No usage limit.
What this tool is for
DNS is the directory that turns your domain name into addresses machines can use. It does not only say where your site is: it also says which server receives your email, which services are allowed to send on your behalf, and which ownership verifications you have carried out.
It is a configuration you set up once and never reread. It then accumulates traces: a record pointing at a former host, an SPF authorising an abandoned mailing service, a verification for a tool uninstalled years ago.
This tool displays the whole of it at once. The common uses are diagnosis after a migration, checking the mail configuration, and confirming that changes have propagated.
Before any migration: lower the TTL to 300 seconds twenty-four hours before the switch. The changeover then becomes almost immediate instead of dragging on for two days, and rolling back stays possible within the minute.
How to read the results
The A and AAAA records give the IPv4 and IPv6 addresses of your site. Having no AAAA is not a fault, but IPv6 has become standard at most serious hosts.
The MX records designate the mail servers, with their priority — the lowest number is tried first. A single MX means an outage loses your mail instead of queueing it.
The TXT records hold most of the mail configuration. Check that SPF, DKIM and DMARC are present: their absence often explains messages that never arrive.
The NS records say who really controls your DNS zone. If they point to a provider you do not recognise, someone else runs your domain — worth checking whenever you take a site over.
The TTL expresses the caching duration in seconds. 3600 means one hour. That value is what determines how long your changes take to propagate.
Common mistakes
Declaring two SPF records. The standard allows only one. Having two invalidates both, and your messages fail the check. Multiple sending services have to be merged into a single record.
Migrating without lowering the TTL first. You end up with some visitors on the old server and some on the new one, for forty-eight hours. On a shop, that means lost orders.
Leaving obsolete records in place. A subdomain pointing at a server that is no longer yours can be taken over by a third party, who will then publish whatever they like under your domain name.
Neglecting DMARC. SPF and DKIM check; DMARC says what to do when a check fails. Without it, every recipient decides alone, with unpredictable results.
Confusing propagation with a configuration error. After a change, wait for the length of the TTL before concluding there is a problem. Plenty of correct configurations are undone by impatience.
Going further
Frequently asked questions
How long does a DNS change take to propagate?
From a few minutes to forty-eight hours, depending on the TTL of the record changed. The TTL says how long intermediate servers keep the answer in memory. Good practice before a migration: lower the TTL to 300 seconds twenty-four hours ahead, then raise it again once the switch has settled.
What are SPF, DKIM and DMARC?
Three TXT records that protect your mail. SPF declares which servers may send on your behalf. DKIM signs your messages cryptographically. DMARC tells recipients what to do when a check fails. Without them your messages land in junk more easily and anyone can impersonate your domain.
Can I have several SPF records?
No, and it is a frequent mistake. The standard allows only one SPF record per domain. Having two invalidates both, and your messages fail the check. If you use several sending services, they have to be merged into a single record.
What is the difference between a CNAME and an A record?
An A record maps a name straight to an IP address. A CNAME points to another name, which is then resolved in turn. A CNAME is convenient when the destination address changes often, as at a cloud host. One constraint to know: a CNAME cannot coexist with other records on the same name.
Why do I have several MX records?
For redundancy. Each MX carries a priority: the lowest number is tried first, the others take over if it does not answer. A single MX means an outage on that server loses your mail rather than queueing it.
Does DNS affect search rankings?
Indirectly, through resolution time: every visit begins with a DNS query, and a slow server adds delay before the first byte. The effect is modest, a few tens of milliseconds, but it adds to everything else. A broken configuration, on the other hand, simply makes the site unreachable.