Modifying cloudns dns records does not take effect

[DarkDeviL]

@ldm1162845582

I initially saw this issue here and the explanation given was that there was a problem with the soa settings:
But now that I have set up the soa parsing correctly it still doesn’t work!

I’m not sure what exactly you mean with this?

As for the stuff that was mentioned in the other thread:

@Laudian

The parent nameservers are set up incorrectly and claim SOA despite the subdomain airport being delegated.

You need to fix the incorrect response of the parent nameservers.

This statement is still correct, and the exact same that goes on for ag.cloudns.nz.

The .cloudns.net name servers are having a SOA record, which means that they are authoritative for ag.cloudns.nz, as well as the sub-domains below that label.

Since the .cloudns.net name servers do not know about test.ag.cloudns.nz, they will return code 3 (NXDOMAIN), for test.ag.cloudns.nz, if that isn’t configured on the .cloudns.net name servers.

Having BOTH the SOA record AND the NS records on .cloudns.net’s side, is the thing that is causing the problem here.

Get the .cloudns.net operators to remove that SOA record, if you want to delegate ag.cloudns.nz (properly) to Cloudflare.