Could not dump example.come zone: zone example.com/IN: NS 'ns1.example.com' has no address records (A or AAAA)

@Starlight

In that case, you shouldn't use the contrib/Listeners/Named/10_named_override_default_ns_rr.pl listener anyway because that listener still add the glue records in all zones which means out of zone data...

Best would be to use your own listener implementing all parts:

Listen on the beforeNamedAddDmnDb instead of the afterNamedAddDmnDb and then:

• Override the SOA record with a substitution
• Set your own NS entries using the i-MSCP built-in template parser
• Set your own glue records using the i-MSCP built-in template parser
• Remove the dmn NS entry block using the i-MSCP built-in template parser (This would allows to discard any further treatment by the Bind9 server implementation regarding this block; block not processed because missing)
• Remove the dmn NS A entry block using the i-MSCP built-in template parser (This would allows to discard any further treatment by the Bind9 server implementation regarding this block; block not processed because missing)

If you code that listener, we could push it and remove the contrib/Listeners/Named/10_named_override_default_ns_rr.pl listener file.

If you don't, I'll code it.

@Starlight

I'm ending with a listener file such as 10_global_ns.pl

Be aware that I've not tested it. it was fully written without any test other than those made in my head.

Edit: New pastbin link (typo issues)
Edit: Again a new pastbin link (typo issues)
Edit: Again a new pastbin link (typo issues)
Edit: Again a new new pastbin link ($ORIGIN must not be used for NS entries)
Edit: Again a new pastbin link (typo issues)
Edit: Replaced pastbin link by gist
Edit: The listener is now available in the 1.3.x branch (see below).

@Starlight

• Fixed
• Fixed
• Nops The loop is run once per IP type. Then, I go to next IP if the type doesn't matches. I do this way to fix the issue exposed in Could not dump example.come zone: zone example.com/IN: NS 'ns1.example.com' has no address records (A or AAAA)

I'll test it anyway if you have no time this evening.

@Starlight

I've tested and it works

My listener config for that test:

Here, $ZONE_NAME is the value of BASE_SERVER_VHOST (panel host).

Result after creating a new customer account (here testme.com)

dns_01.png

And for the panel zone

dns_02.png

@Starlight

The new listener that allows to set identical NS entries in all zones has been pushed in our repository (1.3.x branch). See https://github.com/i-MSCP/imsc…2f2ab2782b9e9dfdb0cd62625

Be aware that this listener file is only compatible with i-MSCP Serie 1.3.x (version >= 1.3.8 which has not been released yet).

Since the last shoot, the listener has been improved a bit to allow arbitrary NS names. This is mostly needed when you use slave DNS servers that are out of your hands, such as the slave DNS servers of your registrar.

I appreciated all your efforts and also your patience to help us to improve i-MSCP. That is much appreciated.

Thank you.

Quote from Starlight

and secondly about your impatience to do my part of the work.

Quote from Starlight

which changes make them only work with i-MSCP 1.3.x? I would like to run it on my current 1.3.7 already and therefore modify it.

I've changed the db.tpl template file to allow arbitrary NS names. The ns prefix is no longer hardcoded in the template file. I'll provide you with a version compatible with i-MSCP 1.3.7 but be aware that ns names will be fixed because the ns prefix is hardcoded in the db.tpl file. Give me some minutes.

@Starlight

See https://gist.github.com/nuxwin…15fe8cfc02c0320cca2ab539d