External hosts are not resolved from a Plesk server: “Name or service not known” or “Could not resolve host”

Symptoms

• nginx fails to start with the error message:

  nginx[58503]: nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "r3.o.lencr.org" in the certificate "/usr/local/psa/var/certificates/scfO1mntc"

• When securing a domain with a Let's Ecnrypt certificate, the operation fails with:

  Could not issue a Let's Encrypt SSL/TLS certificate for example.com
  Failed to connect to the Let's Encrypt server https://acme-v01.api.letsencrypt.org.
  Please try again later or report the issue to support.

  Details

  Could not obtain directory:

• When installing a Plesk license, the operation fails with:

  cURL cannot communicate with license server https://id-00.kaid.plesk.com:443/ (): Couldn't resolve host name(6) cURL cannot communicate with license server https://id-00.kaid.plesk.com:443/ (): Couldn't resolve host name(6) (Error code: 2)

• On attempt to connect to any external host using the cURL utility, the command shows:

  # curl -I http://example.com
  curl: (6) Could not resolve host: example.com

Cause

The DNS resolver specified in the file /etc/resolv.conf cannot resolve domain names.

Resolution

1. Connect to the Plesk server via SSH.

2. Open the file /etc/resolv.conf in a text editor. In this example, we are using the vi editor:

   # vi /etc/resolv.conf

3. Comment the invalid resolver out by placing a # (hash) character at the beginning of the line.

   #nameserver 203.0.113.2

4. Add a different DNS resolver, for example Google public DNS server:

   #nameserver 203.0.113.2
   nameserver 8.8.8.8

5. Save the change and close the file.

   Note: /etc/resolv.conf can be overwritten on Ubuntu 18.04 and higher by netplan and systemd-resolved.services.

6. Retry the previously failed operation.

   Note: If the above solution does not help, contact your service provider in order to check the network setup.