Hi, @bryanjhickey. There is an explanation for why the NETLIFY type DNS record for the apex domain (renegademma.com.au) was not working.
It appears that the original NETLIFY type DNS record that existed was deleted. Then an A record was created for that same domain name. Then a NETLIFY type record was created again … while the A record for the same name was present.
It is that last step where the failure occurred. The NETLIFY type record cannot be created if there is an A record for the same name (and there was).
We have an open issue to resolve this behavior and, in the meantime, our support team can manually fix the issue.
If this happens again in the future, there is a workflow to resolve it on your own:
- Delete any conflicting A records for the NETLIFY type records.
- Delete any non-working NETLIFY type records.
- Delete the custom domains for the non-working records from the site settings (under Site Name > Settings > Domain management > Custom domains).
- Add the custom domain back to the site setting again (the same place where they were just deleted).
The key to the workflow above is that you are adding the custom domain to the site when there are no conflicting A records and the NETLIFY type records (just the non-working ones) have already been deleted. This recreates any missing NETLIFY records and, now that all conflicts are deleted, the newly created NETLIFY type record will work correctly.
I’ve tested to confirm it is working now. If there are any other questions, please let us know.