Creating new Virtual Server creates a DNS zone that shuts down BIND

New Centos 7 installation, Virtualmin 6.01.

When creating a new virtual server, the created DNS zone has invalid data in it (the word none), that will not allow bind/named to restart. In order to get it back up, I have to manually edit the zone file and remove it.

Below is the file created. (I have changed the IP address and ns for display here). Note the line that says “none”

$ttl 38400 @ IN SOA ( 1507924138 10800 3600 604800 38400 ) @ IN NS @ IN NS IN A IN A IN A IN A IN A IN A IN MX 5 IN TXT "v=spf1 a mx ip4: -all" none IN A IN A

What’s in your Server Templates in the BIND DNS Domain section?

I can’t see how “none” would show up unless you’ve actually got “none” in the extra records field.

This is a NEW install, with NOTHING added that is not out of the box. I checked the skeleton bind section and there is nothing added at all.

I also saw the word none in a thread on a problem in this thread:

Although this is a NEW install and there is NOTHING added in the BIND section of the server templates skeleton, I notice above the NONE appears after SPF in the zone file. In the Bind Section of the template, after SPF and DKIM, there is a button that is checked as NONE in the Added named.conf directives for new zones. I wondering if it is taking it literally.

Huh, yeah, that’s interesting and new. I haven’t seen this behavior. I’m gonna try to reproduce it. That issue is all over the place, so I doubt Jamie will even notice the issue with ‘none’ since there’s like a half-dozen other issues being discussed in one ticket. :wink:

I’ll see if I can figure out how to trigger this, and hand it off to Jamie to fix if I can’t spot why it’s messing up.