Dear TWW IT folks,

Trying to load http://sdreefs.comsdreefs.com on my home desktop with no luck. It worked before and then all of the sudden it stopped and I just get the chrome "Oops! Google Chrome could not find http://www.sdreefs.com" which is odd because it works on my phone, tablet, and work laptop. It seems I don't have problems anywhere else.

Any ideas?

[Edited on August 16, 2013 at 2:09 AM. Reason : link]

8/16/2013 2:05:43 AM

On Windows, go to Command Prompt, type

ipconfig /flushdns

8/16/2013 2:54:25 AM

Thanks for the quick reply... unfortunately no dice. I am using windows 7 and I know the site isn't down because I just pulled it up on my phone. Now it says:

This webpage is not available

The webpage at http://www.sdreefs.com/ might be temporarily down or it may have moved permanently to a new web address.
Error code: ERR_NAME_RESOLUTION_FAILED

8/16/2013 3:08:11 AM

Quote :

"ERR_NAME_RESOLUTION_FAILED"

This indicates some sort of DNS problem; maybe the address that Chrome has cached in its own DNS resolver is now wrong, so you could try restarting Chrome.

Now when you say that it works on your work laptop, did you try it on the same network connection as your home desktop?

Also, what DNS servers do they use? You can find this out by typing

ipconfig /all

192.168.1.1 (router)
8.26.56.26 (Comodo Secure DNS, pulled from router settings)
8.20.247.20 (Comodo Secure DNS, pulled from router settings)
156.154.70.22 (old Comodo Secure DNS, pulled from router settings)

8/16/2013 3:23:30 AM

you could have a virus on your computer that fucked your dns settings.

8/16/2013 4:19:37 AM

Guessing you use Google DNS. They've been having a bunch of issues since yesterday from what I read.

8/16/2013 9:09:05 AM

alexwbush, going back a few steps in basic troubleshooting-- did you try a different browser? browsers will cache DNS resolutions, and flushing your windows DNS cache probably won't clear that out. If IE or Firefox are successful, then it's your Chrome DNS cache. If not, it's something else, quite possibly what FroshKiller said.

--

slightly off-topic, but a co-worker shared this with me yesterday

https://code.google.com/p/namebench/

ended up switching from google DNS to OpenDNS-- cut my DNS latency by half.

not really noticeable for most things, but it really helps with sites that do a shitload of http requests for multiple hostnames. (cough cough, looking at you cisco.com)

8/16/2013 9:36:46 AM

I had a problem where I got the same error... I'm trying to remember if I checked the site on my tablet or another browser to confirm it was up. It was also every site, not just one. I tried flushing the DNS cache and all that, but the only thing that worked was completely uninstalling chrome, rebooting and reinstalling.

I was stumped.

8/16/2013 4:55:37 PM

Check my DNS settings as you suggested. I am set up with 8.8.8.8 and 8.8.4.4

I am using an ethernet connection plugged through a router. I tried plugging directly into the cable model, still no luck. I have tried chrome and internet explorer, neither can find the page on this computer.

8/16/2013 7:09:56 PM

Try going to command prompt and typing "ping websitename.com" and see if you can get a response outside of the browsers?

8/17/2013 1:01:41 AM

Quote :

"Try going to command prompt and typing "ping websitename.com" and see if you can get a response outside of the browsers?"

Ping request could not find host sdreefs.com. Please check the name and try again.

8/17/2013 3:01:41 AM

^^good point

You can also test DNS servers other than the ones you've set yourself up with by using the nslookup command, like

nslookup sdreefs.com 8.26.56.26

8/17/2013 3:03:19 AM

^I typed in the nslookup command and got:

Server: ns1.recussive.dns.com
Address: 8.26.56.26

Non-authoritative answer:
Name: sdreefs.com
Address: 72.214.27.23

And I checked LAN settings and I am not set up to use a proxy server.

8/18/2013 2:10:25 AM

I just tested this out myself (BTW it's recursive there, not "recussive") and found that Google Public DNS still has problems; I get the same message as you do when trying out 8.26.56.26, but when I try 8.8.8.8 I get this:

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

*** google-public-dns-a.google.com can't find sdreefs.com: Server failed

Server:  resolver4.opendns.com
Address:  208.67.220.222

Non-authoritative answer:
Name:    sdreefs.com
Address:  72.214.27.23

8/18/2013 4:05:41 AM

unlikely, but what does your hosts file look like?

8/18/2013 11:28:37 AM

Maybe I missed it, but your tablet you used, is that WiFi only? That is to say it, did you get there over the same network?

I'm guessing its isolated to just your computer.

8/18/2013 8:09:33 PM

I've been able to access via wifi on tablet, phone, and another laptop all on the same network

8/18/2013 10:46:21 PM

Did you try this:

Quote :

"set one DNS server to Google Public DNS (which usually is good) and the other to OpenDNS"

Try 8.8.8.8 and 208.67.222.222 for starters and it should work (sdreefs.com is still unavailable through Google Public DNS, but it's a good choice to keep around for when it starts working again).

8/18/2013 11:13:05 PM

4.2.2.2 and 4.2.2.4 are other easy to remember servers.

> sdreefs.com
Server: 4.2.2.2
Address: 4.2.2.2#53

Non-authoritative answer:
Name: sdreefs.com
Address: 72.214.27.23
> 72.214.27.23
Server: 4.2.2.2
Address: 4.2.2.2#53

Non-authoritative answer:
23.27.214.72.in-addr.arpa name = sandiegoreef.net.

[Edited on August 20, 2013 at 3:00 PM. Reason : ]

8/20/2013 2:57:14 PM

^In fact, 4.2.2.1 all the way to 4.2.2.6 are open to the public; still it might be better to use nameservers operated by different entities (the ones I just mentioned are all from Level-3).

The commands that Grandmaster showed off are from the interactive mode of nslookup, and the only difference in Windows is that you don't see explicitly that it makes a request on UDP Port 53 (the default port for DNS).


BTW I just checked again, and sdreefs.com doesn't show up in Google Public DNS...it used to be so reliable

8/20/2013 5:50:09 PM

I've got somewhat similar issues going on 10 months. This occurs across all computers and I've flushed both Windows and browser DNS cache.

Basically attempts to connect to sites like youtube and google maps kill my connection. Like in the task manager you'd see a connection going at max speed for 3 seconds, then completely off for 3 seconds (dl and ul). I also get anywher from 10 to 15% packet loss when attempting to connect to those sites.

Edit: The task manager thing I mentioned above looks like this:

Where it should be solid.

Other sites are perfectly fine, no problems. Doesn't matter what time of day, same behavior, so I don't think it's a load issue. Unless the network here is constantly pegged.

The line has been tested multiple times and it is supposedly fine but youtube might as well be blocked it sucks so much.

I came across a site that mentioned that certain ISPs throttle sites like youtube and it recommended to block certain IPs to alleviate the issue. This didn't work in my case.

Edit:
I've also tried manually setting the DNS to 8.8.8.8 (IIRC) and removing the setting, allowing it to default to the ISP's DNS - no change in behavior.

[Edited on August 22, 2013 at 5:17 PM. Reason : -]

8/22/2013 5:09:59 PM

o dag

Google Public DNS still fails when trying to go to sdreefs.com

9/15/2013 7:36:48 PM

turned out to be a router issue. I swapped routers, website works fine.

10/9/2013 1:37:35 AM

^^^you might have malware. First thing I'd try though if its affecting all your computers on the network is swapping a new router in (or flashing the firmware with an updated version on the router you currently have)

10/9/2013 1:41:51 PM

^It affects all computers, even a fresh install of Windows. I've since moved on to a completely different router, same problem persists.

Other than hounding AT&T every single day replacing all the telephone cabling in my house is the next step.

Most of the time things are fine. The connection begins to flake any time you try to do multiple things at once. The connection really begins to flake with youtube and google maps. I no longer try to browse youtube from home, it will load a few seconds, timeout, and not recover without a refresh - then it's the same thing all over again.

10/9/2013 1:52:33 PM

just tested again

sdreefs.com is not recognized by Google Public DNS

what a joke

10/10/2013 6:01:26 AM