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

DNS problems

M

MikkyX

Guest
Hi,
After resolving my little qmail problem I've run headlong into another brick wall.

My DNS server shows in Plesk as running - and if I start it myself via /etc/init.d/named start (or restart) , it comes up and says OK - so it's evidently up and running.

However if I try to ping, traceroute, dig - anything - nothing happens. IP numbers for ping work fine.

As a result my box is unable to communicate with any other server on the Internet - stuff coming IN to the box is fine - websites and incoming mail are good. My problem is nothing can LEAVE the box.

Anyone got any suggestions before I tear what little hair I have left from my head?
 
Anyone got any suggestions? My mail queue is growing and it's getting quite bad :(
 
This isn't a problem with your DNS Server, it's a problem with your /etc/resolve.conf.

Test your DNS Server like this: dig @localhost google.com

Test your /etc/resolve.conf nameservers through dig google.com.

To correct this problem, replace the nameserver xx.xx.xx.xx; as outlined in /etc/resolve.conf with your own (localhost, for example), which will cause all DNS Queries to hit your DNS server instead of the world.
 
That seems to have done the trick - thanks. :)

My resolv.conf now includes nameserver 127.0.0.1 which means all DNS goes through my local box.

Why would resolv.conf get overwritten like that though - and to addresses which couldn't be traced via their IP?
 
Back
Top