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

named.conf will not be updated

techwide

New Pleskian
I have successfully upgraded Plesk from 9.x to 10.0.1.
Everything seems to be working fine.

However once a domain has expired, there will be a problem with DNS.

When I re-activate the suspened domain, the named.conf entry does not get updated, hence the domain won't be recognised.

Has anyone experienced such problem?

To me this is a bug in Plesk 10.0.1.
 
Could you please describe this problem with more details and step-by-step instruction for reproducing?
 
Hi IgorG,

Let me explain again.

1. When domain hosting expires, Plesk removes the domain entry from named.conf.
2. I activate manually but the domain entry does not get updated. <= I see this is the problem
3. Hence the domain cannot be resolved.

I fixed this problem by re-entering the entry in named.conf and restart named

Hope you understand this problem.

Regards,
Peter
 
I can't reproduce it:

1. Suspend subscription and domain:

# /usr/local/psa/bin/domain --webspace-off test.com
# grep test.com run-root/etc/named.conf
zone "test.com" {
file "test.com";

Unsuspend subscription and domain:

# /usr/local/psa/bin/domain --webspace-on test.com
# grep test.com run-root/etc/named.conf
zone "test.com" {
file "test.com";
 
If you manually suspend and unsuspend (or activate) it will seem updating named.conf without a problem.
You must set the expiry date for the domain and let the system pass overnight.
Then you will see the problem.
 
Had a similar problem but it related to being able to create subdomains but them not being correctly set up in Plesk's nameserver records. Tried to restart BIND, wouldn't work. Discovered that named.conf (/var/named/run-root/etc/named.conf) wasn't updating. Looked in /var/messages and saw this:

named: /etc/named.conf:172: zone '0.0.127.in-addr.arpa': already exists previous definition: /etc/named.conf:82

Removed duplicate entries and restarted BIND (/usr/local/psa/admin/bin/dnsmng --start).

Worked.

3 days of grief fixed in an instant. Now I can sleep.
 
Back
Top