• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue resolv.conf with error after reboot

Jürgen_T

Jürgen_T

Regular Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.44_build1800220614.18
After reboot the resolv.conf appears obviously wrong as follows:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.1nameserver 127.0.0.53

How can I achieve this order after reboot:

nameserver 127.0.0.1
nameserver 127.0.0.53
 
You must log in or register to reply here.

Similar threads

I
Issue Connectivity issues in Ubuntu Server 22.04
2 3
Replies
51
Views
19K
trialotto
T
Mark12345
Issue DNS Settings bind9 nameserver 127.0.0.1 slow http API calls
Replies
1
Views
3K
Mark12345
Mark12345
Jürgen_T
Question resolv.conf problems with Ubuntu 22.04 LTS
2
Replies
26
Views
59K
D3nnis3n
D
LionKing
Resolved cURL Error (6) Could not resolve host: accounts.google.com
Replies
2
Views
8K
LionKing
LionKing
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
5K
kassi
K
Back
Top