I should also say that I flushed the dns cache using ipconfig/flushdns but this did not help.

Yes, when using Open DNS, and using a webbased Nslookup at KLOTH.net, I get the IP address

DNS server handling your query: localhost
DNS server's address: 127.0.0.1#53

Non-authoritative answer:
Name: rei.com
Address: 206.81.220.22
When I cut and paste 206.81.220.22 into the address bar of firefox, it says connecting to rei.com and then fails after about 30 secs with:

The connection has timed out

The server at www.patagonia.com is taking too long to respond.

I have turned off my firewall, flushed the dns cache, and looked at the hosts file, which just has one entry :
127.0.0.1 localhost

But when I go back to DNS server = 0.0.0.0 then I can get to rei.com
I get the trouble when trying internet explorer too.
thanks for any advice
scoulter

I could not get a valid response using the windows nslookup, even on websites that worked. I guess I don't know what I am doing there. went to cmd prompt, typed nslookup rei.com.

open dns server addresses are configured on my router.

I have rebooted the router, powered it down and back up, and did release and renue.

The porn filtering does work for me.
thanks
thanks

C:\>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : stup4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lighttube.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : lighttube.net
Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
Physical Address. . . . . . . . . : 00-0E-A6-4B-A9-38
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.196
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Saturday, September 19, 2009 4:02:59
PM
Lease Expires . . . . . . . . . . : Sunday, September 20, 2009 4:02:59 P
M

C:\>

then nslookup

C:\>nslookup rei.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.0.1: Timed out
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: rei.com.lighttube.net
Address: 208.67.216.132


C:\>
router is dlink 655

@ ihateopendns66
Turn it off the same way you turned it on. Remove the server addresses from router or computer.



@ scoulter
DNS Suffix Search List. . . . . . : lighttube.net
Connection-specific DNS Suffix . : lighttube.net
Remove these from TCP/IP config.

Your nslookups are failing at your router.
*** Can't find server name for address 192.168.0.1: Timed out
nslookup rei.com. <--- Note the trailing dot.

Ok, I have learned a little more about how to use nslookup and get to it's special prompt.

When DNS server is 0.0.0.0 then
> nslookup rei.com
DNS request timed out.
timeout was 2 seconds.
Server: rei.com
Address: 206.81.220.22 (and this did go to rei.com when cut and paste into address bar, so this worked)

When using Open DNS server at 208.67.222.222 then
> nslookup rei.com
Server: rei.com.lighttube.net
Address: 208.67.216.132

DNS request timed out.
timeout was 2 seconds.
*** Request to rei.com timed-out
>

So it looks like Open DNS is having some sort of trouble and I just plan to use 0.0.0.0 until they get it sorted out.

Is there any sort of cache I need to clear, etc, or other action to take?
Thanks

Refer to the two posts prior to your last one. It isn't an OpenDNS problem.

As @maintenance already said "It isn't an OpenDNS problem", if nslookup returns 206.81.220.22 with OpenDNS enabled. So it turns out to be a local problem, probably browser related. Have you tried another browser too?

"how/where do I change DNS Suffix Search List. . . . . . : lighttube.net..."
Start > Settings > Control Panel > Network Connections > Ethernet adapter Local Area Connection > Properties > Internet Protocol (TCP/IPv4) > Properties > Advanced > DNS

and the lighttube.net is most likely being propagated by your router.. check for it there and remove it.. you should only need it at modem level..

What is your connection (or your computers connection) with lighttube.net ?
Perhaps that has something to do with it...

Well I have kept trying different things. I was able to remove lighttube.net from the connection specific dns and dns suffix search list.

Windows IP Configuration

Host Name . . . . . . . . . . . . : stup4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : .

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : .
Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
Physical Address. . . . . . . . . : 00-0E-A6-4B-A9-38
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 69.196.210.101
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 69.196.210.1
DHCP Server . . . . . . . . . . . : 69.196.210.1
DNS Servers . . . . . . . . . . . : 69.196.208.8
69.196.208.10
Lease Obtained. . . . . . . . . . : Wednesday, September 30, 2009 10:23:
06 AM
Lease Expires . . . . . . . . . . : Wednesday, September 30, 2009 1:21:1

This did not help.

Also now even opendns.com is having trouble loading, taking a couple of minutes and then in a simple text format.

moved over to a Ubuntu machine on my network and rei.com would not load when using opendns servers for dns. would load if dns was 0.0.0.0

Turned off firewall, Norton Internet Security, this did not help.
Reflashed my router.

Strangely, when looked at the "failed to load screen" in firefox, I turned off Ad Block Plus extension, and when Firefox reloaded, REI.com came up. When I tried REI.com myself a moment later, it would not come up.

Disconnected router, plugged this PC directly into Ethernet, in TCP properties set DNS to open dns and could not load rei.com.

then set TCP properties to obtain DNS server address automatically, then and REI.com would load quickly.

any advice would be appreciated. maybe my ubuntu experience offers a clue.

I have the dlink dir-655 router running firmware version 1.21,hardware version A3. I am in middle TN and ISP is lighttube.net, a fiber to the home service from our local utility. Ethernet comes from their box up to my router.
Thanks

Somehow my watchguard soho6 router was assigning a DNS suffix from an old isp that I didn't even have anymore. I checked the router settings and the dns suffix box was blank.

I added a "." to the field as suggested in this forum and now the strange dns suffix is replaced by a dot when I view connection details in windows. I hope this fixes my issue. I was getting a dns error in event viewer.

I looked at the openDNS router set up instructions and none say anything about the dns suffix. Why not?

most cases it is no matter, but some routers seem to decide to go ahead and pass the domain handed to them by the ISP, when it is usually not needed past the router.. adding the . if it is available is the same as configuring the third DNS Server address, it prevents the router from picking up the Domain suffix that is passed to it via WAN..
the thing is that xp seems to know to not use the domain suffix for domain names with a TLD without the period, but Vista/7 apply the suffix unless you manually add a period.. doesn't seem to affect web browsing though usually.. just confined to nslookup.. and probaly just a change that microsoft did to make it behave as it should instead of being kludged.. similar to how they fixed some of the stuff in IE that tended to end up breaking some poorly done websites..

None of the components is wrong for itself, just the combination.

rotblitz can you elaborate? I'm seeing different behaviour depending on the DNS I'm using. Something's not right somewhere.
Really annoying as I consider myself to be pretty proficient with networking!

Still doesn't explain why the nslookups against the ISP's DNS resolve but against OpenDNS fail. Ain't technology wonderful! (and yes, I'd already found that link ;-) )

"They do not fail! You just have to append the trailing dot to make an FQDN, for both, your ISP and OpenDNS. You fail doing this. "

Quite deliberately! The basic assumption I have is if I can do "nslookup www.google.com.au" against my ISP DNS and get the expected result then I should be able to do the same against the OpenDNS one.

It'll be a few weeks before I can have another look.
Thanks for the input.

>>The basic assumption I have is if I can do "nslookup www.google.com.au" against my ISP DNS and get the expected result then I should be able to do the same against the OpenDNS one.<<

That reminds me of how my FORTRAN teacher, long time ago, insisted we start each FORTRAN program with the words "ASSUME NOTHING".

Anyway, it looks like your ISP gets too many queries from people who do not use nslookup properly, so their DNS server strips the additional nonsense that nslookup (and perhaps other Windows software) appends.

If so, it may be useful to their customers, but it is non-standard behavior, as it is not the job of a DNS server to assume, no matter how intelligently, what people meant instead of what people (and their software) typed. And since it is non-standard, OpenDNS is correct in the way it responds to your queries.