• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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
6K
trialotto
T
Mark12345
Issue DNS Settings bind9 nameserver 127.0.0.1 slow http API calls
Replies
1
Views
2K
Mark12345
Mark12345
Jürgen_T
Question resolv.conf problems with Ubuntu 22.04 LTS
2
Replies
26
Views
30K
D3nnis3n
D
Oscar Segura
Issue Upgrading from Ubuntu 20.04 to 22.04: failed reboot
Replies
0
Views
4K
Oscar Segura
Oscar Segura
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
2K
kassi
K
Back
Top