• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Open DNS servers

S

swgatl

Guest
When I do a dnsreport on any of the domains hosted on my server at http://www.dnsreport.com I get an fail error on the Open DNS servers part.

ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:

Server ***.***.**.66 reports that it will do recursive lookups. [test]
Server **.***.**.67 reports that it will do recursive lookups. [test]


See this page for info on closing open DNS servers.

I'm not sure what I need to do about this because my 7.5.4 server didnt have this problem. It only started when I moved to my new server with 8.0.

Any ideas on how to fix this on a live server?

Thanks,
Cody
 
You need to add the following line to the options section in your /etc/named.conf file:

allow-recursion { 192.168.0.0/24; 127.0.0.1; };

This prevents access for resolving DNS to only those addresses/networks listed - customise as necessary. You may want at least 127.0.0.1 but if you don't want anything then enter:

allow-recursion { none; };

Plesk shouldn't overwrite anything in the options section.
 
Originally posted by crossconnect
You need to add the following line to the options section in your /etc/named.conf file:

allow-recursion { 192.168.0.0/24; 127.0.0.1; };

Plesk shouldn't overwrite anything in the options section.
Thanks :)
 
Back
Top