slow "Resolving host"

[klch]

Ever since I switch to Sonic FTTN from ATT Uverse 12Mbps, I noticed every time I enter a website in the browser, it's taking more than a whole seconds to "Resolving host...". It was never that slow when I was using Uverse, or it was quick enough that was not noticable.

Anyone notice that?

[Guest]

Ever since I switch to Sonic FTTN from ATT Uverse 12Mbps, I noticed every time I enter a website in the browser, it's taking more than a whole seconds to "Resolving host...". It was never that slow when I was using Uverse, or it was quick enough that was not noticable.

Anyone notice that?

No, even when I used AT&T's DNS hardcoded tot he gateway. Culprit points to your DNS or something on your machine.

[dherr]

Make sure you don't have your hosts set to use sonic resolvers:

nameserver 208.201.224.11
nameserver 208.201.224.33
nameserver 75.101.19.196
nameserver 75.101.19.228

Out here in FTTN land we can't use them. We are seen as being "off network" to Sonic now.

[johns]

I had a similar issue resolving only sonic.net sites, before I switched from Fusion to Fusion FTTN. That was the case whether I was using sonic's DNS, or Google's, or OpenDNS. It was't a huge deal, about a 20 second wait, and I didn't notice it until I was planning the switch to FTTN, so I didn't do anything about it.

Johnny

[klch]

my hosts file is basically empty(all lines commented out) just as any "stock" windows is.
and I didn't change any of the DNS setting, just use whatever is default of came with the gateway.

[dherr]

my hosts file is basically empty(all lines commented out) just as any "stock" windows is.
and I didn't change any of the DNS setting, just use whatever is default of came with the gateway.

If that gateway is a Pace 5031nv then you might be experiencing slowdown due to the less than perfect DNS service that this gateway provides. The DHCP provided name server will be the IP of the gateway (192.168.x.x) and thus will be using the caching nameserver on the gateway itself instead of letting your computer go directly to the AT&T name server(s).

The firmware is locked so that you can not manually edit the DHCP provided name server setting and thus you would need to update each client computer. So, if you want to try this, you would use whatever name servers you want, but the closest will be the AT&T set:

nameserver 68.94.156.1
nameserver 68.94.157.1

[bobrk]

Ever since I switch to Sonic FTTN from ATT Uverse 12Mbps, I noticed every time I enter a website in the browser, it's taking more than a whole seconds to "Resolving host...". It was never that slow when I was using Uverse, or it was quick enough that was not noticable.

Anyone notice that?

Yes, I noticed that. First I noticed that the Sonic DNS wasn't working after Sonic discovered it was still accessible by FTTN users, and turned it off for them.

First I tried the AT&T DNS (hardcoded into the modem), but it was slow and inadequate.

Then I tried both Google DNS and OpenDNS. They seem about even and I settled on OpenDNS.

https://developers.google.com/speed/pub ... docs/using

https://www.opendns.com/premium-dns/

I have the DNS servers programmed into my router which is connected to the AT&T access point through the DMZ option on the modem. Works great when the modem is working fine.

[kgc]

At home on my FTTN service AT&T's name servers consistently outperform all of the available public name servers.

dns.png (45.87 KiB) Viewed 12076 times

[bobrk]

I found the benchmarking to be inconclusive, and when I noticed the problem was when I was trying to access both web sites and Neflix content from my AppleTV.

[klch]

Thanks for the advice everyone!
I started using my own router and set the DNS to the ones from Open DNS, and it's much faster than before. Now the delay is virtually not noticable.