Thank you for your answer @luke. Answers below.
Even if the app console says it is?
Even if DNS console says it is?
dalinet.explorer.uns.network domain point to the same IP adress (answered by Netlify DNS of course), and
sandbox.explorer.uns.network is included into the TLS certificate, but not
$ dig +short A dalinet.explorer.uns.network
$ dig +short A sandbox.explorer.uns.network
Ok, I understand you don’t support subzone delegation. So it should be forbidden to register such subdomain as Netlify DNS because it’s too confusing if it doesn’t work!
Remember, it has been working for months (at least the 9 last) for several domains and websites, so, from a client’s point of view, it’s a regression. Maybe that was working by chance, anyway, it was working.
Otherwise, can you explain why
sandbox.explorer.uns.network domain is not affected by the issue?
We can’t delegate the whole
uns.network domain, as we have other subdomains and subzones handled elsewhere.
Today, we can only delegate subdomain, such as
Thank you for reading so far