• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Unable to find DNS Resolver

  • Thread starter Deleted member 190352
  • Start date
D

Deleted member 190352

Guest
Server operating system version
Plesk Obsidian 18.0.73
Plesk version and microupdate number
Update #3 Web Host Edition
I'm looking to make Quad9 my only resolver on my server.

I've edited /etc/systemd/resolved.conf, but it still defaults back to Google and I don't want it to.
Apparently this could something to do with Plesk/Ionos, my Hosting provider.

Does anyone know anything about this or where can I find the DNS Resolver to hopefully fix this.
 
Thanks. Yes I did work on that. AI gave me some good pointers.
In the end, getting the right DNS Resolver was the issue. The Fallback I was leaving open but it was defaulting to Google all the time.
The culprit was the Netplan. Once I put the right IP's in there, the problem was fixed and Spam Assassin should now stop sending emails because of DNSBL checks. Google didn't support Open Resolvers.
 
You must log in or register to reply here.

Similar threads

bigbear67
Question Network routing issue after update (loss of default route source IP / DNS failure on Ubuntu 24.04)
Replies
0
Views
2K
bigbear67
bigbear67
N
Issue Enabling DNSSec for existing keys -- Workaround for double plesk bug.
Replies
10
Views
1K
tessa67
tessa67
M
Question IONOS as secondary dns?
Replies
6
Views
7K
mopanim
M
finbarr69
Question Plesk keeps re-enabling IPV6
Replies
3
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
first4it
Issue Docker containers unable to resolve DNS or access external network on Plesk Obsidian 18.0.76 Update #4 (Collabora / Nextcloud issue)
Replies
2
Views
5K
first4it
first4it
Back
Top