ISPconfig version: 3.1.2 I created DNS records by ISPconfig to get the DNS zone file, and then I deleted the zone and try import function, finally the NS records in the zone are missing and error as "Writing BIND domain file failed: /var/named/pri.abc.com zone abc.com/IN: has no NS records zone abc.com/IN: not loaded due to errors.". Below is the zone file content: Code: $TTL 3600 @ IN SOA ns1.def.com. test.test.com. ( 2017032201 ; serial, todays date + todays serial # 7200 ; refresh, seconds 540 ; retry, seconds 604800 ; expire, seconds 3600 ) ; minimum, seconds ; abc.com. 3600 TXT "v=spf1 mx a ~all" abc.com. 3600 MX 10 mail.abc.com. abc.com. 3600 NS ns1.def.com. abc.com. 3600 NS ns2.def.com. mail 3600 A 1.2.3.4 www 3600 A 1.2.3.4 abc.com. 3600 A 1.2.3.4
I've never used that zone import feature, sorry. If you have a recent ispconfig manual, see what it says for that section; the NS records are obviously there, so it must be getting stripped out/replaced or something.
Have you made a dns / full resync afterwards? I normally do that when changes are made to dns zone files manually. May be that could help?
Are the ns records missing just in the zone file, or are they missing also in the list of records of that zone that you see in the ISPConfig interface?
Thanks till, They are missing both in zone file and also in ISPConfig interface, you may check screenshots below. To duplicate the problem, you can simply copy the zone file content in my first thread above, and then save it as abc.com.txt , and then import it to ISPConfig
Maybe the import strips NS records for some reason? Have you tried just adding the two NS records in the ISPConfig interface and see if the zone file is then created? If you have a lot of zones that may need to be scripted (and/or the import process looked at?), but it might get you moving towards resolving the issue.
Yes, if I add NS records in ISPConfig interface after import, the zone is created. Never mind, in fact i thought submitting problem here can help ISPConfig better.
One year later and same happens exactly you describe. Using the version 3.1.11! At the bug tracker, dont see any update for this problem... Can you confirm what happens @till ? Regards.
