How to check propagation of DNS records for a Plesk domain?

Plesk for Windows DoNotDelete:docref kb: how-to Plesk for Linux Ideal

Question

How to verify if a DNS record of a Plesk domain is resolvable globally?

Answer

It is possible to check propagation of any DNS record by using an online checker tool or by executing the nslookup console command on your computer.

Note: DNS changes can take up to 48 hours to fully propagate globally.

1. Using an online checker:

The following examples are DNS Checker tools that can be used for Free, that will show DNS Results from multiple servers globally, which is often best for reviewing the full DNS propagation cycle world-wide, DNSChecker, DNS Propagation Checker, etc.

To check a record:

1. Select the required type (A, MX, TXT, etc.).

2. Enter the record name in the corresponding field.

For example, checking an acme-challenge record for issuing Let's Encrypt certificate would be as follows:

Type: TXT
Domain record: _acme-challenge.example.com

Note: Replace example.com with the actual domain name

2. Using the nslookup console command on your computer:

On Mac OS or Linux, use the built-in Terminal app.
On Windows start the Command Prompt.

To check A DNS record

Execute the command below to define to which IP address the A DNS record of example.com resolves to:

# nslookup example.com 8.8.8.8

In the last Address fields there will be the required IP addresses - IPv4 and/or IPv6:

# nslookup example.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: example.com
Address: 203.0.113.2
Name: example.com
Address: 2001:db8:f61:a1ff:0:0:0:80

To check MX DNS record

Execute the command below to define the MX DNS record of the domain example.com:

# nslookup -q=MX example.com 8.8.8.8

In the output the MX DNS record value of example.com which is mail.example.com will be displayed:

# nslookup -q=MX example.com 8.8.8.8
...
Non-authoritative answer:
example.com mail exchanger = 10 mail.example.com.

To check TXT DNS record

Execute the command below to define the TXT DNS record of the example.com domain:

# nslookup -q=TXT example.com 8.8.8.8

In the below line all the existing TXT DNS records of example.com will be listed:

# nslookup -q=TXT example.com 8.8.8.8
...
Non-authoritative answer:
example.com text = "wgyf8z8cgvm2qmxpnbnldrcltvk4xqfn"
example.com text = "v=spf1 -all"

There can be specific TXT DNS records that should be queried a bit differently.

For the acme-challenge TXT DNS record required for issuing a Let's Encrypt certificate, use:

# nslookup -q=TXT _acme-challenge.example.com 8.8.8.8
...
Non-authoritative answer:
_acme-challenge.example.com text = "AC7rCwwNIMGiQLwFD0Kxx5ySmahKMMSCDKaqTq5B9BU"
For the DKIM record:

# nslookup -q=TXT default._domainkey.example.com 8.8.8.8
...
Non-authoritative answer:
default._domainkey.example.com text = "v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDVKMuI4LI9lSZTYLonVQ/L2nXY6NjpTT1A3lucWEWOT7w33KE8+1OydTgtIr8FLq26exL2LezTSSf1DnFsJqivEVzOaItl0moJHqtXXPGcm8jppXVZpiM4JxvwK5wA+FW+DnsTKhVTIhhIw1kyc9/Od0RZpXp9qYTiIP1DjxT2sQIDAQAB;"

To check TLSA DNS record

Execute the command below to define the TLSA DNS record:

# nslookup -q=TLSA _25._tcp.mail.example.com 8.8.8.8

It will be displayed in the Non-authoritative answer section:

# nslookup -q=TLSA _25._tcp.mail.example.com 8.8.8.8
...
Non-authoritative answer:
_25._tcp.mail.example.com rdata_52 = 3 1 1 CE8E87D32FBD54323C51FB94D07C24450398EBD9A9407F567146B3E7 9DDC86C9

Articles in this section

Question

Answer

Comments

Articles in this section

Question

Answer

Related articles