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

Left over domain.com in named.conf

Lloyd_mcse

Silver Pleskian
Plesk Guru
Hi guys,
I've been trying to resolve an issue on one of my servers running Ubuntu 12.04.5 LTS, i originally installed Plesk 11.5.30 and upgraded to Plesk 12 a couple of weeks ago.
Long story short I notice there are some left over zones in named.conf...

Code:
zone "domain.com" {
    type slave;
    file "s/domain.com.bak";
    masters {
        192.168.1.1;
    };
};

zone "0.168.192.in-addr.arpa" {
    type slave;
    file "s/0.168.192.in-addr.arpa.bak";
    masters {
        192.168.1.1;
    };
};

And no that is not sanitised, that's exactly how it is in the named.conf file.
Obviously I don't have a domain called domain.com and 192.168.1.1 has never been our internal network or router IP.

Looking in /var/named/run-root/etc/named.conf.default it contains the same zones.

I have just removed the zones from named.conf, and restarted bind.

I assume it's a bug, so thought I should post the info.
Regards

Lloyd
 
Back
Top