Dapper Install Delays Resolving Domain Names

RAdams · 08-18-2006, 10:49 AM

When typing a web address such as "google.com" into a web browser or "ping google.com" into terminal, there is a 10-15 second delay before the domain name is resolved. The latency after the domain name is resolved is normal (~30 ms for pinging google.com) Typing in an IP address directly resolves very quickly. I know when this happens in Windows, the WINS Socket Layer has to be reset via terminal commands. What do I do in Ubuntu?

fragos · 08-18-2006, 10:54 PM

By default Ubuntu tries both IPv4 and IPv6. It tries v4 after it determines v6 isn't available by a timeout. This particularly impacts DNS response time. It should help if you disable IPv6.

"sudo gedit /etc/modprobe.d/bad_list" with the following text:

#added to disable IPV6
alias net-pf-10 off

RAdams · 08-19-2006, 04:38 AM

Quote:

Originally Posted by fragos

By default Ubuntu tries both IPv4 and IPv6. It tries v4 after it determines v6 isn't available by a timeout. This particularly impacts DNS response time. It should help if you disable IPv6.

"sudo gedit /etc/modprobe.d/bad_list" with the following text:

#added to disable IPV6
alias net-pf-10 off

Makes perfect sense. When I get back to the office Monday I'll give that a go. In the meantime... hurrah for the weekend!

fragos · 08-19-2006, 02:00 PM

DNS response varies by ISP even on a broadband network. I saw an article on this on Digg. Comcast was rated very fast and Verizon was four to five times slower which Verizon denies.

RAdams · 08-21-2006, 09:27 AM

Quote:

Originally Posted by fragos

DNS response varies by ISP even on a broadband network. I saw an article on this on Digg. Comcast was rated very fast and Verizon was four to five times slower which Verizon denies.

You win. Changing my bad list worked like a charm.

Yeah, Verizon sucked, I heard. I wonder how their FiOS network is working out?

I have RoadRunner right now, and I must say it's nice and smooth.

We have Comcast (formerly Suscom) at work. It seems okay...

RAdams · 08-28-2006, 09:35 AM

UPDATE:

The problem was also alleviated greatly using the instructions at http://ubuntu.wordpress.com/2006/08/...ster-browsing/. I had actually already done these steps when I disabled the ipv6 protocol check, so I didn't realize how significant the steps in the above link are until I did a re-install on this box. (Nuclear option fix for xorg crashes, anyone?)