Topic 'Re: [AZ] DNS Results return' in forum 'Cox' - dslreports.com

Re: [AZ] DNS Results return

Wed, 24 Dec 2014 16:10:07 EDT

ThreeD posted : I have been having the same slow dns lookup that you are describing here in the Palos Verdes, CA area of Cox. I have tried various dns servers and combinations, and it is better, but still not good. I am slowly coming to the conclusion it is something that Cox is doing. It seems to go away and get faster late at night. The issue goes away if I am not on Cox, such as using my laptop away from home. I don't know what it is, but it seems to be an issue with Cox.
--
My goal in life is to be as good of a person as my dog already thinks I am.

Re: [AZ] DNS Results return

Tue, 23 Dec 2014 13:42:22 EDT

whosmatt posted : I actually switched from 4.2.2.x DNS to google's servers after I started getting redirects from the former. It's sporadic, but using DNSBench still occasionally shows redirects from one or more of the 4.2.2.x servers for me.

Re: [AZ] DNS Results return

Tue, 23 Dec 2014 13:32:34 EDT

Rakeesh posted :

said by dvd536:

4.2.2.1 / 4.2.2.2
no redirects nor do you have your browsing info sold to the highest bidder.

Umm....8.8.8.8 doesn't do any of that. It can't do any of that. It's just name resolution.

So say for example you are having one of your typical mornings and you want your Alex Jones daily snake oil pitch, and your browser asks the resolver in your OS to ask the name server what IP address belongs to www.infowars.com.

Your resolver then asks 8.8.8.8 (or whoever) what IP address corresponds to www.infowars.com, to which it responds 208.100.25.88. You can test this by plugging 208.100.25.88 into your web browser and seeing the same website you already see every other minute.

This information isn't terribly useful for tracking browsing info because it gives NO indication WHATSOEVER about where exactly you are going, or who is going there.

So for example, if you hit www.alexjones.com/buymyfluoridesnakeoil/ or www.alexjones.com/aliensarecontrollingus/, 8.8.8.8 can't tell the difference, because that kind of information is never sent across the wire by your resolver. Furthermore, it can't tell if you went there, or if your dad went there, because again, that information is never sent across the wire. It also can't tell whether you went there with your web browser, or if you just pinged it (this traffic is 100% identical as far as the DNS server is concerned.)

As for redirecting, 8.8.8.8 is NOT known by anybody to do that. In fact that is one of few DNS providers who are known to properly implement the NXDOMAIN response these days.

Re: [AZ] DNS Results return

Tue, 23 Dec 2014 13:08:47 EDT

odog posted :

said by zipturtle:

Traceroute doesn't do anything since that isn't the issue, it is response from the DNS servers which appears to be an issue or perhaps more accuratly, the IP's being returned are themselves being delayed due to some sort of restriction.

Que? So the Google DNS servers weren't resolving the queries quickly? Did you try doing a traceroute to see the path it is taking? The Google DNS design uses anycast, so it is possible you were hitting the "wrong" 8.8.8.8, and or taking an asymmetric path.

I'm not sure what Level3s policy is with respect to DNS result tracking/data retention. I suspect they have similar policies to OpenDNS, and Google in that they farm the data on a more general level rather than specific user tracking.

Re: [AZ] DNS Results return

Tue, 23 Dec 2014 09:53:09 EDT

zipturtle posted : I am currently using 4.2.2.1 and 4.2.2.3 which I had switched to before I first posted, this is where I noticed sites loading much faster.

Traceroute doesn't do anything since that isn't the issue, it is response from the DNS servers which appears to be an issue or perhaps more accuratly, the IP's being returned are themselves being delayed due to some sort of restriction.

Sites like ESPN now fly open without waiting for connections where they used to load most of the page and then be waiting for other content which was being delayed.

As for browsing info, kinda of short sighted since what do you think the websites are doing.
--
Kevin - Using Cox Business Services for phones and Internet. Servers now in a remote data center.

Re: [AZ] DNS Results return

Tue, 23 Dec 2014 07:26:22 EDT

dvd536 posted : 4.2.2.1 / 4.2.2.2
no redirects nor do you have your browsing info sold to the highest bidder.
--
Despises any post with strings.

Re: [AZ] DNS Results return

Mon, 22 Dec 2014 16:21:04 EDT

odog posted : which google DNS?(anycast 8.8.8.8?) How does a traceroute look?

[AZ] DNS Results return

Mon, 22 Dec 2014 15:45:39 EDT

zipturtle posted : For some time now, I have directed DNS requests to Google. I've noticed over the past month what I thought were slow returns from servers that I was seeing here at the house, but not other places. Example ESPN where the page was taking a long time to load only to find that if I stopped the loading almost everything was already.

Today, I switched name servers for testing and found that sites I thought were slow were actually waiting for their DNS to come back first.

Anyone else having issues with using Google DNS in the Phoenix metro area? Not sure if this is just a Google issue or some sort of delay caused by Cox.
--
Kevin - Using Cox Business Services for phones and Internet. Servers now in a remote data center.