• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Issue with the domain resolving

YSA

New Pleskian
Hello,

In Plesk for an alias domain 'salvationarmybarrie.ca' we noticed a following warningunder 'DNS Settings' menu - Domain is not resolvable [1]. Recently we chnaged NS records for this domain but there's already passed 2 days, so DNS propagation should be completed but problem still exists. Also we noticed that this domain doesn't still doesn't resolve from 2 places in China: DNS Checker - DNS Check Propagation Tool .

We've already checked for solution described on link Plesk shows "Domain is not resolvable" message for the domain that resolves correctly but there's no 'IPv6 address' menu there and currently only IPv4 is using on server. Could please let us know what may causes this issue and how it can be solved?

Thanks.

[1]
scr.JPG
 
I have checked your domain and found the following:

- domain is really not resolvable:
Code:
# host salvationarmybarrie.ca
Host salvationarmybarrie.ca not found: 2(SERVFAIL)
- the following nameservers are used for this domain:
Code:
# whois salvationarmybarrie.ca | grep 'Name Server'
Name Server: w3.barrieweb.net
Name Server: w4.barrieweb.net
- with the commands:
Code:
# dig @w3.barrieweb.net salvationarmybarrie.ca
# dig @w4.barrieweb.net salvationarmybarrie.ca
I found that there is correct A records for this domain on these nameservers:
Code:
;; ANSWER SECTION:
salvationarmybarrie.ca. 86400   IN      A       65.21.122.58
So, I suppose that the reason may be on the registrar side. Therefore I suggest you look at this video with a good explanation of how DNS should be configured on Plesk:
 
Back
Top