DE

↑ ↓ select, Enter open, Esc close

Check DNS propagation across public resolvers

harmlessDNSdebian, ubuntu
Adjust the values, the command updates live
user@server
for ns in 1.1.1.1 8.8.8.8 9.9.9.9 208.67.222.222; do echo "$ns: $(dig +short @$ns example.com A | tr '\n' ' ')"; done

Sends the same query to four large public resolvers and prints the answers side by side. After a DNS change, this quickly shows whether the new values have propagated or old entries are still cached.

Note: Resolvers cache until the old TTL expires. Lower the TTL well in advance of planned migrations.

Also searched as

  • how to check dns propagation
  • has my dns change propagated
  • domain still points to old ip

Related one-liners

All in DNS

Check a domain's DKIM key in DNS

$dig +short default._domainkey.example.com TXT
harmlessDNS

Check if a server IP is on the Spamhaus blacklist

$dig +short $(echo 203.0.113.10 | awk -F. '{print $4"."$3"."$2"."$1}').zen.spamhaus.org
harmlessDNS

Check the CAA record of a domain

$dig +short example.com CAA
harmlessDNS

Check whether DNSSEC works for a domain

$dig @1.1.1.1 +dnssec example.com SOA | grep -E "flags:|RRSIG|status:"
harmlessDNS

Compare the SOA serial on all nameservers

$for ns in $(dig +short example.com NS); do echo "$ns $(dig +short @$ns example.com SOA | awk '{print $3}')"; done
harmlessDNS

Look up the MX records of a domain

$dig +short example.com MX
harmlessDNS

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.