.com, .net, etc.

[DoomFinger]

After my uverse install, my computer takes for ever to find an address when I do not enter the end of a URL (.com, .net) when I type them in to Safari, Firefox, Flock, etc.  For example, when I type "cnet" it take for ever to look up and navigate to "cnet.com."  Ideas?

[spd2demun ACE - Master]

Did you not have a problem before with your previous provider?

I can do it with FF, Safari, and IE...maybe someone else has some ideas?

Is your connection up to speed?  Post your stats here for us if you'd like from speedtest.net

[showtime48 ACE - Guru]

i thought you always had to put in the extension. i just tried it and got the ' internet explorer cannot display web page' error...

[spd2demun ACE - Master]

It may be browser settings, like Auto Complete or Allow Friendly HTTPs--it works in all of mine; but that's why I was asking if the OP could do it before, or did it just seem to be a lag issue with speed?

[MarkShadid]

---

showtime48 wrote:
i thought you always had to put in the extension. i just tried it and got the ' internet explorer cannot display web page' error...

---

I just learned something new myself.  I thought you had to put the ext in.

[DoomFinger]

Sorry for the underwhelming amount of details.  To address some of the questions asked:

- Before the switch to AT&T, 99% of the time, just entering the address without the extension would work.  The few times it didn't, I got a Ro@d Runner search listing, as T!me W@rner was my old service provider.  

- The LAN has not changed.  The RG runs to an Apple Time Capsule (802.11n), which is bridged to an Airport Extreme (802.11b/g).  Previously, the same configuration was used, but the Time Capsule plugged into the T!me W@rner modem.

- The RG is set to have the Time Capsule on DMZPlus.  The wireless feature of the RG is disabled.

- The computers in question are Macs.  Safari and Firefox are able to fetch URL's without entering the extension.  IE 8, to my knowledge, cannot.   

- The connection is good.  According to speedtest.net, I'm getting ~5000 down.  Not sure what the up is, but it is what was paid for. 

Message Edited by DoomFinger on 09-29-2008 07:59 AM

[bsdsmb]

I tried this on my mac - and mine seems to be working okay.  I cannot exactly figure out how Safari is guessing URL's - without putting a sniffer on the line.  I think they are doing it with a series of DNS lookups (where they stick on the usual .com, .org, .net).  Hence, you might try looking to see what your mac has as its preferred DNS servers.  This would correspond to your prior note that you would occasionally receive search results that clearly were being inserted on behalf of your former ISP - when they would return a "false positive" - fooling Safari.

You can find that info in your System Preferences | Network | Advanced | DNS tab or simply type the following at a prompt in terminal:

#cat /etc/resolv.conf

You might then also try timing DNS responses to see if yours are for some reason unusually slow.  I'm currently using 2 routers stacked in series before my AT&T DSL line.  The initial router for my mac is an aging Airport Extreme base station.  It is relaying my DNS - so my DNS servers are reported as (at the mac computer) my base station.  My base station in turn is using AT&T's primary DNS servers as relayed automatically from them.

You can try a couple of tests yourself (in the terminal) by using the "dig" command.

#dig www.yahoo.com

#dig www.google.com

and so and and so forth.

I was finding that popular sites like those above are getting responses in around 95 ms.  When I picked a more obscure site that likely is not cached - my responses are more like 110 ms.  If you are getting responses way slower than that - that is likely the source of your trouble, and you need to figure out how your DNS resolution is happening in your network - with all those various apple tid bits you have.

Good luck.

[RCSMG ACE - Master]

I use FF and I just type in part of the site and it completes the rest.