|
|
|
|
|
|
by dichardson
3532 days ago
|
|
|
Perhaps Google had old (but valid) records still in their cache for a while. Google DNS was working for me for a while, and then stopped. Apparently Dyn has the problem fixed, but maybe there is some TTL based propagation delays still. I updated my internal network to use Dyn's internet guide/public DNS and the problem is fixed. Maybe this is their strategy: we break it, you buy it ;) https://help.dyn.com/internet-guide-setup/ If you can't load that page, the public DNS servers are:
216.146.35.35, 216.146.36.36 |
|
|