FAQ on "Buggy DNS"

If you were referred to this page by test-ipv6.com, it means that we were able to detect a dangerous condition with your DNS server.

First a description of the problem:

This is bad for several reasons:

So, what is actually affected?

You'll need to determine what device is forwarding your DNS queries.

With Windows, at the cmd prompt, you can type ipconfig /all. Look for "DNS Servers".

With Linux, BSD, and Mac OS X, you can do this in a terminal: cat /etc/resolv.conf.

Residential ISP customers: look to see if the DNS server is 192.168.0.1 or 192.168.1.1. If so, chances are good that your home router is at fault. This is probably the blue box you have that connects the Internet.

Business customers: Provide this information to your IT professional to investigate.

IT professionals:

You can see an illustration of this, by doing:


dig aaaa buggydns1.test-ipv6.com  @192.168.1.1
dig a buggydns1.test-ipv6.com @192.168.1.1

Substitute the 192.168.1.1 with the resolver being used by the host. If the "aaaa" request comes back with no answer, but the "a" answer does, this is a confirmation of a broken DNS cache or forwarder. The actual DNS information for buggydns1.test-ipv6.com has only an IPv6 record configured.


Copyright (C) 2010, 2024 Jason Fesler. All rights reserved. Version 1.1.983 (3ee0173)
Mirrors | Source | Email -   - Attributions | en_US
This is a mirror of test-ipv6.com. The views expressed here may or may not reflect the views of the mirror owner.