Can't access website, but everyone else can?

By Pattack
in Smart Home, Network & Security

 Share

Recommended Posts

Rookie

Pattack

Posted
Posted

Hi!

For a while I've bee trying to access soundcloud.com but can't. I thought it might have been a problem with the site itself, but I went to http://www.site24x7.com/ping-test.html and saw that it was up and working and issoundclouddown.com and it says that its up. So, I thought it might be a problem in my country or my provider but I tested it out with my friends and it worked. I can ping the ip number of the site but cant visit the site itself.

Everyone (4 different computers) who is on our house's router cant access it for some reason. I checked with my provider and they said its accessible and working, and I checked my router and we dont have any ip filters, url blockers or firewalls activated (for testing sake). I tried going into Command and entering ipconfig /release and ipconfig /renew, but it didnt work either.

What am I missing?

tldr: I cant access soundcloud.com (in any browser), but its up for everyone else.

Rookie

Pattack

Posted
  • Author
Posted
  On 07/06/2011 at 01:11, Fus10n said:

Have you checked your host file, someone could be messing with you..

Thanks for the reply!

I just checked and there are no entries of the ip, neither soundcloud.com . And this problem for everyone connected to my router (so, that would mean different host files). I tried resetting the router to update the dns, but it still wont access.

Any clues?

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

Does it resolve or not? Can not tell from you post

From a cmd line try and ping it, do you see an IP come back?

C:\Windows\System32>ping soundcloud.com

Pinging soundcloud.com [178.249.137.64] with 32 bytes of data:

Reply from 178.249.137.64: bytes=32 time=121ms TTL=54

Reply from 178.249.137.64: bytes=32 time=128ms TTL=54

Reply from 178.249.137.64: bytes=32 time=121ms TTL=54

See it resolves to 178.249.137.64

What do the computers on your network do? Also what does the output of nslookup look like?

example

C:\Windows\System32>nslookup

> soundcloud.com

Server: pfsense.local.lan

Address: 192.168.1.253

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

Rookie

Pattack

Posted
  • Author
Posted
  On 07/06/2011 at 01:43, BudMan said:

Does it resolve or not? Can not tell from you post

From a cmd line try and ping it, do you see an IP come back?

C:\Windows\System32>ping soundcloud.com

Pinging soundcloud.com [178.249.137.64] with 32 bytes of data:

Reply from 178.249.137.64: bytes=32 time=121ms TTL=54

Reply from 178.249.137.64: bytes=32 time=128ms TTL=54

Reply from 178.249.137.64: bytes=32 time=121ms TTL=54

See it resolves to 178.249.137.64

What do the computers on your network do? Also what does the output of nslookup look like?

example

C:\Windows\System32>nslookup

> soundcloud.com

Server: pfsense.local.lan

Address: 192.168.1.253

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

Thanks for replying!

When I put nslookup soundcloud.com I get this:

nslookup soundcloud.com
Server:  UnKnown
Address:  192.168.0.1

*** UnKnown couldn't reach soundcloud.com: Server failed

"UnKnown"? Weird. Does this mean anything?

When I ping soundcloud.com I get:

ping soundcloud.com
Ping request could not find host soundcloud.com. Verify the name and try again.

But when I ping the IP address, I get this

ping 178.249.137.64

Pinging 178.249.137.64 with 32 bytes of data:
Reply from 178.249.137.64: bytes=32 time=265ms TTL=46
Reply from 178.249.137.64: bytes=32 time=269ms TTL=46
Reply from 178.249.137.64: bytes=32 time=251ms TTL=46
Reply from 178.249.137.64: bytes=32 time=260ms TTL=46

Ping statistics for 178.249.137.64:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 251ms, Maximum = 269ms, Average = 261ms

Any ideas?

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

Just because you can ping the address means you have connectivity, but you can not resolve it is your problem.

Do this

nslookup

> server 4.2.2.2

Default Server: vnsc-bak.sys.gtei.net

Address: 4.2.2.2

> soundcloud.com

Server: vnsc-bak.sys.gtei.net

Address: 4.2.2.2

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

Does that work, 4.2.2.2 is just a open dns - you could also try 8.8.4.4, 8.8.8.8 googledns or opendns 208.67.222.222 208.67.220.220

> server 8.8.8.8

Default Server: google-public-dns-a.google.com

Address: 8.8.8.8

> soundcloud.com

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

Address: 8.8.8.8

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

192.168.0.1 I would assume is your router, not a fan of soho router dns, the feature normally seems like an afterthought to most makers I have seen, and rarely do they give you any soft even interface to check what is cached, or even flush the routers cache.

I would assume your router is pointing to your ISP dns? You could try changing your router to use some other dns other than your ISPs, you could have your machine directly use say opendns, googledns, etc. But your problem is clearly an issue with resolving the host. So no the website is never going to work -- manysite do not actually work if you try and access by IP.. Do neowin even - looks like crap :)

post-14624-0-65749700-1307416281.jpg

Other than verification of able to access the server on port 80, using an IP address for a website rarely is a good test. For example your soundcloud.com does not work by IP either -- well kind of it redirects you to a developers.soundcloud.com when you access via http://178.249.137.64 but since your not resolving soundcloud.com its unlikely you could resolve developers.soundcloud.com.

Another thing you can do when you have problems with resolving sites is do a whois to see owning nameservers of the domain, and then directly query them. example

Domain Name: SOUNDCLOUD.COM

Registrar: GODADDY.COM, INC.

Whois Server: whois.godaddy.com

Referral URL: http://registrar.godaddy.com

Name Server: NS00.S-CLOUD.NET

Name Server: NS01.S-CLOUD.NET

Name Server: NS02.S-CLOUD.NET

So if I query one of those owning server directly

> soundcloud.com

Server: ns01.s-cloud.net

Address: 178.249.137.54#53

Name: soundcloud.com

Address: 178.249.137.64

Notice comes back authoritative.. Not a cache from the nameserver I queried. You need to figure out your issue with nameresolution of soundcloud.com and then you will be able to access..

post what you get when you change your servers to 4.2.2.2 or opendns or googledns and if that works will walk you though how to do more troubleshooting to what is actually the problem.. What is the make and model number of your router btw?

Rookie

Pattack

Posted
  • Author
Posted
  On 07/06/2011 at 03:19, BudMan said:

Just because you can ping the address means you have connectivity, but you can not resolve it is your problem.

Do this

nslookup

> server 4.2.2.2

Default Server: vnsc-bak.sys.gtei.net

Address: 4.2.2.2

> soundcloud.com

Server: vnsc-bak.sys.gtei.net

Address: 4.2.2.2

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

Does that work, 4.2.2.2 is just a open dns - you could also try 8.8.4.4, 8.8.8.8 googledns or opendns 208.67.222.222 208.67.220.220

> server 8.8.8.8

Default Server: google-public-dns-a.google.com

Address: 8.8.8.8

> soundcloud.com

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

Address: 8.8.8.8

Non-authoritative answer:

Name: soundcloud.com

Address: 178.249.137.64

192.168.0.1 I would assume is your router, not a fan of soho router dns, the feature normally seems like an afterthought to most makers I have seen, and rarely do they give you any soft even interface to check what is cached, or even flush the routers cache.

I would assume your router is pointing to your ISP dns? You could try changing your router to use some other dns other than your ISPs, you could have your machine directly use say opendns, googledns, etc. But your problem is clearly an issue with resolving the host. So no the website is never going to work -- manysite do not actually work if you try and access by IP.. Do neowin even - looks like crap :)

post-14624-0-65749700-1307416281.jpg

Other than verification of able to access the server on port 80, using an IP address for a website rarely is a good test. For example your soundcloud.com does not work by IP either -- well kind of it redirects you to a developers.soundcloud.com when you access via http://178.249.137.64 but since your not resolving soundcloud.com its unlikely you could resolve developers.soundcloud.com.

Another thing you can do when you have problems with resolving sites is do a whois to see owning nameservers of the domain, and then directly query them. example

Domain Name: SOUNDCLOUD.COM

Registrar: GODADDY.COM, INC.

Whois Server: whois.godaddy.com

Referral URL: http://registrar.godaddy.com

Name Server: NS00.S-CLOUD.NET

Name Server: NS01.S-CLOUD.NET

Name Server: NS02.S-CLOUD.NET

So if I query one of those owning server directly

> soundcloud.com

Server: ns01.s-cloud.net

Address: 178.249.137.54#53

Name: soundcloud.com

Address: 178.249.137.64

Notice comes back authoritative.. Not a cache from the nameserver I queried. You need to figure out your issue with nameresolution of soundcloud.com and then you will be able to access..

post what you get when you change your servers to 4.2.2.2 or opendns or googledns and if that works will walk you though how to do more troubleshooting to what is actually the problem.. What is the make and model number of your router btw?

When I use googledns it works! I cant access soundcloud.com normally!

I have a kronnus wireless-n router. Specifically a Kr-rw513n1 (rev A 2.0)

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

And did you try using different dns? google, open? I posted exactly how to do it.

Yeah its clearly a dns problem - lets fix it, did you try just rebooting your router. It could be a bad cached NS record.

Rookie

Pattack

Posted
  • Author
Posted
  On 07/06/2011 at 13:38, BudMan said:

And did you try using different dns? google, open? I posted exactly how to do it.

Yeah its clearly a dns problem - lets fix it, did you try just rebooting your router. It could be a bad cached NS record.

Yes, I tried all 3 opendns's that you posted and they worked and fixed the problem! I typed them in my router's dns manually, and then I could access soundcloud.com again.

I tried rebooting the router (before entering the opendns manually, using just my ISP's dns), and no go. Still couldnt access the site.

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

^ I highly doubt malwarebytes would remove his ability to resolve the site. He posted both a ping and nslookup output that showed him NOT resolving the site to an IP. If running active sort of antimalware/antivirus sure it could block a specific site - but it would be listed in said softwares logs, and I don't see it preventing resolution of the name?? I guess it could - but have not seen this, and since changing his router to point to a different dns than his ISP fixed his problem - that clearly was not the case ;)

So Pattack your up and running now using a different dns than your ISPs - so thread /closed? or do you still have issues/questions?

Its quite possible your ISP has a bad cache for the NS for that domain -- I find many ISPs dns infrastructure not up to the task of handling all their users quite often, and it seems to be a service that gets neglected quite often in upkeep and maintenance.

Pointing your router to use a public dns or one of the many services out there be it google, open or comodo, etc. Is good fix -- many of these services even allow you to block bad sites, etc. And depending on your location on the planet should not cause you any sort of delays in name resolution since many of these services provide nameservers in strategic locations across the globe for fast response times.

Also as I mentioned before many soho routers dns forwarding/caching service is not very good and you might be better off just pointing each client to an outside DNS.

Rookie

Pattack

Posted
  • Author
Posted
  On 07/06/2011 at 14:57, BudMan said:

^ I highly doubt malwarebytes would remove his ability to resolve the site. He posted both a ping and nslookup output that showed him NOT resolving the site to an IP. If running active sort of antimalware/antivirus sure it could block a specific site - but it would be listed in said softwares logs, and I don't see it preventing resolution of the name?? I guess it could - but have not seen this, and since changing his router to point to a different dns than his ISP fixed his problem - that clearly was not the case ;)

So Pattack your up and running now using a different dns than your ISPs - so thread /closed? or do you still have issues/questions?

Its quite possible your ISP has a bad cache for the NS for that domain -- I find many ISPs dns infrastructure not up to the task of handling all their users quite often, and it seems to be a service that gets neglected quite often in upkeep and maintenance.

Pointing your router to use a public dns or one of the many services out there be it google, open or comodo, etc. Is good fix -- many of these services even allow you to block bad sites, etc. And depending on your location on the planet should not cause you any sort of delays in name resolution since many of these services provide nameservers in strategic locations across the globe for fast response times.

Also as I mentioned before many soho routers dns forwarding/caching service is not very good and you might be better off just pointing each client to an outside DNS.

Yep! That fixed it. Theres no problem using an open dns right? Like, an security holes or anything like that?

Either way, I really want to thank everyone in this thread for helping me out. You guys rule!

Grand Master

+BudMan MVC

Posted
  • MVC
Posted

No is not security issue for sure - if anything you should be more secure because you can block bad sites via dns. Now I personally don't like how they redirect google, but I do believe you can disable that feature now on their dashboard if you setup an account (free) - but I would not really call that a security issue. I run my own dns so I don't have a need to use opendns or any other outside dns.. but I use them quite often in troubleshooting and like their site where you can check their cache.

http://www.opendns.com/support/cache/

I run my own local dns, both unbound and bind and now and then windows and play with some other nameservers now and then djbdns (tinydns), I normally never forward to any specific nameservers unless troubleshooting something. So my servers don't do any forwarding. I have dnssec enabled and need to be able to do dns over ipv6 and since I work with and just plain love dns! I run my own - not suggesting you should or anything.

But I would not have suggested opendns or google or even 4.2.2.2 if I felt there was any sort of security problem with them.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.