How to Check DNS Records with the Plesk DNS Inspector

After changing DNS records in Plesk, you need to verify those changes went live. This guide covers how to check DNS records in Plesk and verify them using command-line tools and online checkers.

Viewing DNS records in Plesk

1. Log in to Plesk.
2. Go to Websites & Domains → find your domain.
3. Click Hosting & DNS → DNS Settings.

This page shows every record in your domain's zone file — A, AAAA, CNAME, MX, TXT, SRV, NS, and SOA records with their types and values.

Checking records with nslookup

The nslookup command (Windows, macOS, Linux) queries DNS servers directly:

• A record: nslookup yourdomain.com 8.8.8.8
• MX record: nslookup -q=MX yourdomain.com 8.8.8.8
• TXT record: nslookup -q=TXT yourdomain.com 8.8.8.8
• CNAME: nslookup -q=CNAME www.yourdomain.com 8.8.8.8
• SRV: nslookup -q=SRV _autodiscover._tcp.yourdomain.com 8.8.8.8
• DKIM: nslookup -q=TXT default._domainkey.yourdomain.com 8.8.8.8

Checking records with dig (Linux/macOS)

dig provides more detail than nslookup:

• dig yourdomain.com A @8.8.8.8
• dig yourdomain.com MX @8.8.8.8
• dig yourdomain.com ANY @8.8.8.8

Online DNS checker tools

These check records from multiple global locations:

• DNSChecker.org — 100+ global servers, supports all record types
• whatsmydns.net — global propagation map
• MXToolbox — best for email records (MX, SPF, DKIM, DMARC)

DNS propagation

Changes take effect on your server immediately, but DNS servers worldwide cache records based on TTL:

• Typical: a few minutes to a few hours
• Maximum: up to 48 hours
• Tip: reduce TTL to 300 before planned changes, then increase after propagation

Important notes

• Plesk shows the zone file, not what the world sees. If nameservers point elsewhere, Plesk records won't be active.
• Flush local DNS cache for fresh results: ipconfig /flushdns (Windows), sudo dscacheutil -flushcache (macOS), sudo systemd-resolve --flush-caches (Linux).
• Use public DNS (8.8.8.8 or 1.1.1.1) to avoid ISP cached results.

Troubleshooting

Record shows in Plesk but doesn't resolve externally:

• Check your nameservers point to Plesk: nslookup -q=NS yourdomain.com
• If nameservers point to an external provider, add records there.
• Ensure you clicked Update in Plesk after changes.

Record shows old value:

• DNS caching — wait for TTL to expire or flush your cache.
• Use 8.8.8.8 to bypass ISP cache.

nslookup returns "server can't find" error:

• The record may not exist. Double-check it in Plesk.
• Try a different DNS server.

Need help? Open a support ticket.