Plesk Webmail Server Not Found - Fix it Now ?

Plesk Webmail Server Not Found - Fix it Now ?

If the Plesk server is not set up to manage DNS the Webmail will not resolve correctly in the global DNS system.
Generally, this error happens when Webmail / domain does not resolve correctly in global DNS system because Plesk server is not set up to manage DNS.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve related Plesk errors.

Nature of Plesk Webmail Server Not Found

Generally, we come across this error while opening webmail/domain in a browser or when we issue Let's Encrypt on the domain.
The error message may differ based on the browser we use.
For instance:
i. Firefox:

"Server not found. Firefox can't find the server at webmail.example.com"

ii. IE:

"Internet Explorer cannot display the webpage"

iii. Chrome:

"Oops! Google Chrome could not find webmail.example.com"




"404 not found"

iv. Let's Encrypt cannot be issued on the domain:

Error: Could not issue a Let’s Encrypt SSL/TLS certificate for example.com. Authorization for the domain failed.
Type: urn:acme:error:connection
Status: 400
Detail: Fetching http://example.com/.well-known/acme-challenge/cCMl-4ZDqnWT-DEADBEEFl0sl_z9KVN_Ghkc1f1pMpQ: Timeout during connect (likely firewall problem)

How to fix Plesk Webmail Server Not Found ?

To verify the root cause, we run the following commands in a command-line interface.

i. Initially, we test if the domain can resolve to an IP address in general:

nslookup example.com
Server: mydns.server.com

Non-authoritative answer:
Name: example.com

ii. However, if we receive the following output, it means that the domain does not resolve properly:

nslookup webmail.example.com
Server: mydns.server.com
*** UnKnown can't find example.com: No response from server

iii. Then, we check if the DNS service on the server with Plesk contains a proper record for the domain:

nslookup webmail.example.com <—- IP address of the server with Plesk
Server: UnKnown

Name: webmail.example.com

Here, if we receive a wrong IP address or nothing at all from the first command, and valid records from the second command, it means the Plesk server does not serve the DNS zone for a domain.

There are two options to resolve the issue:

1. Set Plesk server to be nameserver of the domain
Generally, we install the DNS Server in Plesk Installer.
If it is not, we follow the steps below and add the DNS Server component to the Plesk configuration:
a. Initially, open UDP port 53 on the system and external firewall.
b. Log into Plesk and find Name Servers in Plesk > Domains > example.com > DNS Settings, take the “value” for the record type “NS”.
c. Then, change the Name Server for our domain at the domain registrar's account.
Some domain registrars require two NS servers with different IP addresses. In such cases, we may experience a problem.

To solve this, there are different ways:
i. Firstly, we can allocate an additional IP address from the Hosting Provider and add it to Plesk. Then use it as an additional Name Server in domains DNS Settings.
For example, ns1.example.com ns2.example.com
ii. On the other hand, we can set up a slave DNS server on additional hosting and connect it to Plesk as a Slave DNS server using the extension.
iii. Similarly, we can use 3rd-party extensions that allow adding DNS zones: Microsoft Azure DNS, DigitalOcean DNS, Amazon Route 53
To find it, go to, Menu Plesk > Domains > example.com > DNS Settings should be available.

2. Add a respective A-record on a registrar/3rd-party DNS side.

[Need urgent help with fixing Plesk errors? We'd be happy to assist you. ]

Who We Are ?

Most prominent, efficient, and well-performing IT companies and software solutions.

Related Posts