[IceEnclosure]

Since about 24 hours ago I could no longer access a particular site from home. It's a DJ site where everyone posts their mixes and remixes, all legal style. I'm a member on the forums there and enjoy myself thoroughly.

Can't access it from home via Comcast, but CAN access it from my windows mobile device. I checked the whois on the site and it seems the registration for the website was renewed YESTERDAY. Could this have anything to do with it? I'm looking at the site right now just fine on my phone, and other people from all over are logged in and doing so from their computers.

Could Comcast have blocked my access to this particular site? I do find loads of music there, often 50-100MB at a time, but they're always downloaded from off-site links, such as zshare. My dad was telling me Comcast does things like this, trying to be like a hero of the internet or something. I've done nothing wrong!! Again, all the music is legal. DJ's often post their sets from gigs they play, or remixes they've made, records they've released etc.

Or am I not seeing what's really going on?


Domain Name: *******.COM
Registrar: TUCOWS INC.
Whois Server: whois.tucows.com
Referral URL: Tucows Domain Name Help Center
Name Server: NS2.POWWEB.COM
Name Server: NS3.POWWEB.COM
Status: clientHold
Updated Date: 21-jun-2007
Creation Date: 19-jun-2004
Expiration Date: 19-jun-2008

>>> Last update of whois database: Fri, 22 Jun 2007 03:33:46 UTC <<<

[Peter]

Why did you hide the URL?
Just curious...

[IceEnclosure]

eh, i dunno. edit: removeded

[Dakarʒ]

Originally Posted by Peter 

Why did you hide the URL?
Just curious...

Yeah, I was wondering myself.

[starman]

DNS change?

[Doofy]

Icy, it seems like it's a server-side problem. I can't get to it either and my ISP doesn't block anything.

Guessing it's DNS issues.

[IceEnclosure]

I don't know what DNS change means, so I can't really respond to it properly.

[Doofy]

Icy, just hang tight for a couple of days and it'll probably remedy itself.

[Dakarʒ]

It's not being found where I work.

[starman]

Essentially, if its "address" changed, it has to propagate to all the ISPs. It might not have gotten to yours yet.

[Doofy]

Originally Posted by Doofy 

Icy, just hang tight for a couple of days and it'll probably remedy itself.

...unlike the NN server, which looks like it's just about to go tits-up.

[IceEnclosure]

hmmph.

[Doofy]

Originally Posted by starman 

Speaking of which, what pic is your sig from?

Something somewhere in the amazon.com lingerie section, IIRC.

[starman]

Originally Posted by Doofy 

...unlike the NN server, which looks like it's just about to go tits-up.

Speaking of which, what pic is your sig from?

[RAILhead]

Safari can’t open the page “http://www.low-bee.com/” because it can’t find the server “www.low-bee.com”.

[IceEnclosure]

well that's good.
at least it's not just me.

[Dork.]

The "D" in "DNS" stands for Distributed, which means that in addition to the authoritative root DNS servers, there are tons of little name servers all over the place that cache requests, easing load on the root servers.

When a server has to change its IP address in DNS, all those little name servers will still have copies of the old IP address, and direct you there. After a few days, those servers will consider those copies "stale" and then go out and check the Root Servers again. When they do that, they'll get the new address.

If you find out the new IP address and just type it into your browser address bar, you can bypass DNS. Sone things on the site may not work properly, though, like links that use the full URL in them, since those will still go to DNS.

[IceEnclosure]

heard, thanks again folks!

[residentEvil]

simple to check: ask your isp what the ip address, and ask the dns host in that whois what the ip is...you can see they are different:

* my isp *

> nslookup www.low-bee.com
Name: www.low-bee.com
Addresses: 206.112.100.151, 64.158.56.38

* whois dns server *

> nslookup www.low-bee.com ns2.powweb.com
Name: www.low-bee.com
Address: 65.254.250.103

new IP hasn't populated to all DNS servers yet...

[residentEvil]

Originally Posted by Dork. 

The "D" in "DNS" stands for Distributed, which means that in addition to the authoritative root DNS servers, there are tons of little name servers all over the place that cache requests, easing load on the root servers.

When a server has to change its IP address in DNS, all those little name servers will still have copies of the old IP address, and direct you there. After a few days, those servers will consider those copies "stale" and then go out and check the Root Servers again. When they do that, they'll get the new address.

If you find out the new IP address and just type it into your browser address bar, you can bypass DNS. Sone things on the site may not work properly, though, like links that use the full URL in them, since those will still go to DNS.

just the IP won't always work since several hundred (thousand) web sites can be on the same IP address via virtual hosts on the web server software.

for example, that IP (the one i showed above, 65.254.250.103 when asking powweb) also hosts: www.bluedot-keesee.com among others.

> nslookup www.bluedot-keesee.com
Name: www.bluedot-keesee.com
Address: 65.254.250.103

[Atomic Rooster]

From Help....



Make sure you have the correct address for the webpage and that you typed it correctly.

Safari may not be able to open a webpage because it doesn't recognize the first part of the address, which identifies the Internet protocol (such as HTTP or HTTPS).

Try entering "/index.html" at the end of the address.

Empty the cache, then try reloading the page.

In some cases a link might open a file in another application. If the file or an application to open the file isn't available, a message says Safari can't open the URL or file. Contact the administrator of the website for help locating the file or the application needed to open it.

Some websites prevent using a browser they do not recognize. Contact the administrator of the website to find out if this is the case.

There may be a problem with the server's configuration. Contact the administrator of the website to find out if this is the case.

[besson3c]

FWIW, you can purge your DNS cache with a:

sudo lookupd -flushcache

[zro]

Damn. Thought it was gonna be a bottle...

[iMOTOR]

Originally Posted by Dork. 

The "D" in "DNS" stands for Distributed, which means that in addition to the authoritative root DNS servers, there are tons of little name servers all over the place that cache requests, easing load on the root servers.

When a server has to change its IP address in DNS, all those little name servers will still have copies of the old IP address, and direct you there. After a few days, those servers will consider those copies "stale" and then go out and check the Root Servers again. When they do that, they'll get the new address.

If you find out the new IP address and just type it into your browser address bar, you can bypass DNS. Sone things on the site may not work properly, though, like links that use the full URL in them, since those will still go to DNS.

I could have sworn that DNS stood for "Domain Name Server".

[OldManMac]

Originally Posted by iMOTOR 

I could have sworn that DNS stood for "Domain Name Server".

That's what I always thought, and according to this it does.

[IceEnclosure]

Originally Posted by Atomic Rooster 

From Help....



Make sure you have the correct address for the webpage and that you typed it correctly.

Safari may not be able to open a webpage because it doesn't recognize the first part of the address, which identifies the Internet protocol (such as HTTP or HTTPS).

Try entering "/index.html" at the end of the address.

Empty the cache, then try reloading the page.

In some cases a link might open a file in another application. If the file or an application to open the file isn't available, a message says Safari can't open the URL or file. Contact the administrator of the website for help locating the file or the application needed to open it.

Some websites prevent using a browser they do not recognize. Contact the administrator of the website to find out if this is the case.

There may be a problem with the server's configuration. Contact the administrator of the website to find out if this is the case.

seriously?

[IceEnclosure]

How do I add the IP address and their site name to my hosts file?

I'm chewing my arm off over here.

[Dork.]

Originally Posted by OldManMac 

That's what I always thought, and according to this it does.

You're right, my bad.... but it is still distributed.

[besson3c]

Originally Posted by IceEnclosure 

How do I add the IP address and their site name to my hosts file?

I'm chewing my arm off over here.

1) sudo nano /etc/hosts

2) Add the following to the bottom of the file:

properIPaddress domainname.com

(note that if you sometimes access the site via www dot yourdomainname you'll need a second entry for this too)

3) sudo lookupd -flushcache

[Dork.]

Originally Posted by besson3c 

1) sudo nano /etc/hosts

2) Add the following to the bottom of the file:

properIPaddress domainname.com

(note that if you sometimes access the site via www dot yourdomainname you'll need a second entry for this too)

3) sudo lookupd -flushcache

This jogs my memory somewhat.... is it possible that lookupd is caching his DNS requests, so even though his upstream DNS provider has the proper information his local copy hasn't been updated yet?

If so, would flushing the lookupd cache without mucking with the /etc/hosts file fix things?

[IceEnclosure]

besson, I put the address in. Let's pretend I don't know EXACTLY what to do next. How do I save the change I made?

[Doofy]

Originally Posted by Dork. 

This jogs my memory somewhat.... is it possible that lookupd is caching his DNS requests, so even though his upstream DNS provider has the proper information his local copy hasn't been updated yet?

If so, would flushing the lookupd cache without mucking with the /etc/hosts file fix things?

Doesn't work here.

[zro]

Originally Posted by IceEnclosure 

besson, I put the address in. Let's pretend I don't know EXACTLY what to do next. How do I save the change I made?

Ctrl-x

y

Return

[besson3c]

Originally Posted by Dork. 

This jogs my memory somewhat.... is it possible that lookupd is caching his DNS requests, so even though his upstream DNS provider has the proper information his local copy hasn't been updated yet?

If so, would flushing the lookupd cache without mucking with the /etc/hosts file fix things?

Yes, it's worth a try...

You can see what is going on by doing a:

host domain.com

in your terminal and seeing how this resolves. If you know of another DNS server, you can compare results by doing a:

host domain.com otherDNSserver

To see what IP your local computer is using, ping the domain name and you should see an IP address listed in the response.

[besson3c]

Originally Posted by IceEnclosure 

besson, I put the address in. Let's pretend I don't know EXACTLY what to do next. How do I save the change I made?

The keyboard commands are listed along the bottom of the nano screen. ^ is the short form for your control key, so control + x will exit, asking you if you want to save the file first.

[IceEnclosure]

it worked, thanks!

so you're saying that at some point I'll have to remove it? (when the issue is resolved)

I only added the one address to the list.

[besson3c]

Originally Posted by IceEnclosure 

it worked, thanks!

so you're saying that at some point I'll have to remove it? (when the issue is resolved)

I only added the one address to the list.

You don't have to remove it, but if you don't requests to that domain name will continue to resolve to the IP you have in this file as long as your system is setup to read data from this file, regardless of any DNS changes.