Originally Posted by Mike – MDDHosting
Resolvers (Google) and Nameservers are similar but not the same thing.
I was not aware of that.
Originally Posted by Mike – MDDHostingYou canÂ’t use GoogleÂ’s resolvers as name servers.
CloudFlare comes to mind – you could use them just as additional dns servers. YouÂ’ll need to make sure your zones stay in sync between them.
How would I go about that? When I look for public DNS servers,
https://www.lifewire.com/free-and-pu…ervers-2626062
I see Cloudfare’s 1.1.1.1, but GoDaddy will not accept that. I asked ChatGPT for help, and it was fairly useless, but did suggest Cloudfare’s one.one.one.one, which Godaddy accepts. But that was the only DNS server GoDaddy would accept that I got from ChatGPT – it gave me several others including dns.google, and dns.quad9.net, but none of them were accepted by GoDaddy. Apparently 1.0.0.1 is another Cloudfare one, but neither that works, nor my guess of one.zero.zero.one.
What do you mean by “YouÂ’ll need to make sure your zones stay in sync between them”? I don’t understand what the zones are. As you can guess, I’m not an IT professional.
Given GoDaddy accepts one.one.one.one, would that add any redundancy, or more likely to cause problems? I accept what you say about DNS outages being very rare, so it’s not worth losing sleep over it. But if I could gain some measure of redundancy, I’d feel a bit happier.
Maybe setting one.one.one.one as the primary, and Ionos’s non-functional ns1045.ui-dns.org as the secondary would be worthwhile as a test. That would mean one.one.one.one is the only workable DNS server, so not a long-term solution, but it would at least prove if one.one.one.one will function. However, I’m concerned what you say about keeping zones in sync, as I don’t have a clue what that means, and it may mean that adding one.one.one.one to GoDaddy’s servers will actually cause problems, not add reliability.