Customers are able to prevent named from starting because of wrong zone entries

[Thomas Becker]

---------------------------------------------------------------
PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE
Plesk 10.4.4 Update #47, CentOS 6 64bit

PROBLEM DESCRIPTION
Customers are able to prevent named from starting because of wrong zone entries.

STEPS TO REPRODUCE (EDIT: This steps does not reproduce it exactly)
1. Customer creates new subdomain in its subscription
2. Name of Subdomain: *.customerdomain.com
3. Document root: doesn't matter
4. After subdomain creation change the "Hosting type" of the subdomain to "Forwarding" and insert for example "customerdomain.com" as "Destination address".
5. Restart named will fail because of incorrect zone

ACTUAL RESULT
Restart named will fail because of incorrect zone

EXPECTED RESULT
Plesk Panel should show a warning message and should not allow users doing that.

ANY ADDITIONAL INFORMATION
I assume the same problem in Plesk 11
--------------------------------------------------------------

 

[IgorG]

Need more details. What exactly is incorrect in zone? Any error messages, logs. etc?
Have you checked it on Plesk 11?

 

[Thomas Becker]

Hi Igor,
I tried to reproduce what customers were able to do now for the second time.
The steps mentioned in my first post seems not to reproduce it exactly.

Here are the logs that belong to the problem caused by a customer and its domain configuration:

named[2772]: dns_rdata_fromtext: xxx.xx.xx.in-addr.arpa:224: near '*.customerdomain.com.': bad name (check-names)
named[2772]: zone xxx.xx.xx.in-addr.arpa/IN: loading from master file xxx.xx.xx.in-addr.arpa failed: bad name (check-names)
named[2772]: zone xxx.xx.xx.in-addr.arpa/IN: not loaded due to errors.

Customers do have ability to administer DNS and domains in Plesk.
Any idea how the customers were able to build such wrong zone?

The problem is that this is preventing named from startup.
After deleting the Forwarding from "*.customerdomain.com" to "customerdomain.com" which the customer created in Plesk, named is starting without problems.