• 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.

reseller DNS, /etc/resolv.conf ?

J

JohnB@

Guest
Hello All:

When giving a reseller his/her own nameservers in Plesk 8, do I add these in
/etc/resolv.conf
as well ?
E.g., my /etc/resolv.conf looks like this:
nameserver 111.22.33.10
nameserver 111.22.77.21
search mydomain.com
....should I add:
nameserver 111.22.33.11
nameserver 111.22.77.22
search resellerdomain.com

Please advise.

John
 
Hi John,

To the best of my knowledge, no you don't need to do anything like that.

When a nameserver is registered for a domain all that happens is that you effectively get a pointer, making nsX.whatever.tld point to a certain IP address.

As long as that IP address is the IP address of your DNS server (i.e. your plesk box) then it will work.

What I'm saying is that there is nothing stopping anyone anywhere in the world creating nameserver records for any domain they own and pointing them to your box. There are no config changes you need to make in order to allow this.

Of course if you have not configured named to prevent recursive DNS then effectively this would allow anyone to hijack the processing power of your box to do their own DNS lookups.

But I may be wrong on all this. Maybe someone else will pipe up with a more definitive answer.

Faris.
 
/etc/resolv.conf is ONLY used to resolve domain name queries inside the server. For example if you ping / traceroute a domain it will query this file to decide what DNS nameservers to query for its results.
 
Back
Top