I am having really bad lag. I went to this site, and this is one of the results I got. I have absoutly no Idea what it is.. help?

Summary of Noteworthy Events + –




Major Abnormalities –

•Your DNS resolver manipulates results for IPv6 addresses








Minor Aberrations –

•Network packet buffering may be excessive
•Your DNS resolver returns IP addresses for names that do not exist






Address-based Tests + –


















NAT detection (?): No NAT Detected +








































Local Network Interfaces (?): OK +














DNS-based host information (?): OK +

Reachability Tests + –





















































TCP connectivity (?): OK +















































UDP connectivity (?): OK +







0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.
0.




Traceroute (?): OK +










Path MTU (?): OK +










Hidden Proxy Detection (?): OK +

Network Access Link Properties + –













Network performance (?): Latency: 89 ms, Loss: 0.0% +










TCP connection setup latency (?): 100ms +










Background measurement of network health (?): no transient outages +













Network bandwidth (?): Upload 980 Kbit/s, Download 10 Mbit/s +




Network buffer measurements (?): Uplink 530 ms, Downlink is good –

We estimate your uplink as having 530 ms of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time.

We were not able to produce enough traffic to load the downlink buffer, or the downlink buffer is particularly small. You probably have excellent behavior when downloading files and attempting to do other tasks.







HTTP Tests + –











Address-based HTTP proxy detection (?): OK +










Content-based HTTP proxy detection (?): OK +










HTTP proxy detection via malformed requests (?): OK +










Filetype-based filtering (?): OK +










HTTP caching behavior (?): OK +
















JavaScript-based tests (?): OK +

DNS Tests + –











Restricted domain DNS lookup (?): OK +










Unrestricted domain DNS lookup (?): OK +










Direct DNS support (?): OK +














Direct EDNS support (?): OK +










DNS resolver address (?): OK +


























DNS resolver properties (?): Lookup latency 90 ms +














Direct probing of DNS resolvers (?): +














DNS glue policy (?): OK +













DNS resolver port randomization (?): OK +
























































































































































































































































































































































































































































































































































































































































































































































































DNS lookups of popular domains (?): OK +










DNS external proxy (?): OK +




DNS results wildcarding (?): OpenDNS –


You appear to be using OpenDNS. OpenDNS, by default, deliberately returns addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 67.215.65.132, which resolves to hit-nxdomain.opendns.com. You can inspect the resulting HTML content here.

This is central to OpenDNS's business model. In order to support an otherwise free service, OpenDNS presents the users with advertisements whenever they make a typo in their web browser. You can disable this behavior through the OpenDNS Dashboard.

The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.

The following lists your DNS server's behavior in more detail.
•www.{random}.com is mapped to 67.215.65.132.
•www.{random}.org is mapped to 67.215.65.132.
•fubar.{random}.com is mapped to 67.215.65.132.
•www.yahoo.cmo [sic] is mapped to 67.215.65.132.
•nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 67.215.65.132.


Another problem with the DNS server is its response to a server failure. Instead of properly returning an error when it cannot contact the DNS authority, the DNS server returns an address of 67.215.66.132. Since transient failures are quite common this can be significantly disruptive, turning a transient failure into a wrong answer without any notification to the application doing the name lookup.
















DNS-level redirection of specific sites (?): OK +



























































































































Direct probing of DNS roots (?):

bump