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

Issue Plesk 17.8.11 & BIND: Plesk allows underscore in hostname, thus breaking zone

burnley

Regular Pleskian
BIND doesn't allow underscore for A, MX, NS and SOA (except for the email address part). The problem is, Plesk doesn't check for the existence of underscore in the hostname when entering those records (tested for A and MX) and, after clicking "Update" button, the zone breaks and named can't reload it. PoC:

[...]
Aug 20 10:59:42 plesk12 named[1402]: zone 1.168.192.in-addr.arpa/IN: loaded serial 1566262782
Aug 20 10:59:42 plesk12 named[1402]: 0dom1.local:20: mx_01.0dom1.local: bad owner name (check-names)
Aug 20 10:59:42 plesk12 named[1402]: zone 0dom1.local/IN: loading from master file 0dom1.local failed: bad owner name (check-names)
Aug 20 10:59:42 plesk12 named[1402]: zone 0dom1.local/IN: not loaded due to errors.
[...]
[root@plesk12 ~]# named-checkzone -k fail 0dom1.local /var/named/chroot/var/0dom1.local
/var/named/chroot/var/0dom1.local:20: mx_01.0dom1.local: bad owner name (check-names)
zone 0dom1.local/IN: loading from master file /var/named/chroot/var/0dom1.local failed: bad owner name (check-names)
zone 0dom1.local/IN: not loaded due to errors.
[root@plesk12 ~]# echo $?
1

Plesk generated zone file:
---CUT HERE---
; *** This file is automatically generated by Plesk ***
$TTL 86400

@ IN SOA ns.0dom1.local. tech.ddns.com.au. (
1566262781 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
10800 ) ; Minimum

0dom1.local. IN NS ns.0dom1.local.
s1.0dom1.local. IN A 192.168.1.240
ipv4.0dom1.local. IN A 192.168.1.240
0dom1.local. IN A 192.168.1.240
mail.0dom1.local. IN A 192.168.1.240
ns.0dom1.local. IN A 192.168.1.240
webmail.0dom1.local. IN A 192.168.1.240
www.0dom1.local. IN CNAME 0dom1.local.
ftp.0dom1.local. IN CNAME 0dom1.local.
mx_01.0dom1.local. IN MX 0 aspmx.l.google.com.
0dom1.local. IN MX 10 mail.0dom1.local.
0dom1.local. IN TXT "v=spf1 +a +mx -all +a:plesk12.ddns.local"
---CUT HERE---

Similar for A record. To reproduce:
- Domain DNS Settings -> Add Record
- For A record type, enter "host_name" in Domain name field and the IP in the IP address field. Click Add, then Update. Plesk will accept the record, but named won't reload the zone.
 
Back
Top