I think I have an issue similar to tristyb on Apex domain stuck on DNS propagation.
I’ve just taken over management of the account and there was an A record on the @ domain pointing to 192.168.X.X, which I presumed was set up by someone testing on their local network previously. The NETLIFY records were there already. I deleted the 192.168.X.X record but then tried
traceroute levellingupstem.co.uk and got
unknown host levellingupstem.co.uk. I then tried turning on the IPv6 to see if this flushed out the NETLIFY records.
It seems to half work because I have:
www.levellingupstem.co.uk | Primary domain | Netlify DNS
But then I also have:
levellingupstem.co.uk | Redirects automatically to primary domain | Awaiting Netlify DNS
dig levellingupstem.co.uk I now get an SOA record, but no A record.
I don’t really want to delete the domain and re-add, because I just set up a load of mail DNS records (SPF, DMARC, etc)!
Any advice on what to do?