Dating 8888

This information is vital to help us to identify the cause of the problem.If Google Public DNS (or any open resolver) has trouble resolving a site, or returns inconsistent answers, sometimes it is because the authoritative name servers are having trouble.For information on confidential reporting and survivor advocacy, visit If you are encountering problems when resolving particular names, and want to verify whether the problem is with Google Public DNS, please try resolve the domain first at: https://dns.Otherwise, please include the output of the command in any communication with the Google Public DNS team.If the last line of the output does list 2060::8888 as the final hop, continue to step 3.For example, if you have trouble visiting ), or visit directly.If these tools identify a name server configuration issue, please contact the owner of the name server to fix it.

If you want to report a problem to our user group, please copy and paste the results of the commands in your email.

Try configuring Google Public DNS for IPv4 to diagnose whether the problem is due to IPv6 connectivity on your network.

If IPv4 works for you, you may want to revert your IPv6 configuration and use Google Public DNS with IPv4 exclusively.

If the last line of the output does list 8.8.8.8 as the final hop, continue to step 3.

Open a command prompt, and run the following command: If the last line of the output does not list 2060::8888 as the final hop, or if there are significant timeouts, there may be a network problem preventing you from contacting our servers.

Leave a Reply