Things they've tried that have not worked: • What is/are the IP address(es) of the DNS(s) you want to use?This is a company DNS server that is given with DHCP, it works well for other people.For example, when you visit Key it must look up the corresponding IP address to that hostname behind the scenes.This query is performed by a Domain Name Server (DNS server) or servers nearby that have been assigned responsibility for that hostname.Some provider require secure (HTTPS) communication. Read their help pages for details and also read provider specific informations below.
DNS, which stands for domain name system, is an Internet service that translates domains names into IP addresses.
No one could figure out a pattern or timeline as to when or why this was happening.
After a ton of research and troubleshooting I believe I have at least discovered all of the root causes. One of the problems I was seeing was that the permissions on the records that were created via the Microsoft dynamic DNS process were hosed up.
I've also tried Google's 184.108.40.206 and 220.127.116.11 (which I found from GRC's DNS Benchmark to be the fastest).
• Have you tried using 18.104.22.168 (google) or any of the Open DNS 2.222 or 2.220?