[RGibson]

Can you tell me were reefcentral went to ?

[arconom]

I guess alot of people seem to be having this problem Including me. I wonder what happen?

[Reefland]

I am not sure what the problem is that you guys are experiencing. What part of the country are you in? What ISP are you using?

Like I mentioned in the other thread, your more than welcome to hang out with us.

[arconom]

I live in NY. I use Road Runner.

[Reefland]

It is with your ISP. Bottom line, RC just changed their IP address and with that means all ISP's have to recognize that www.reefcentral.com points to a new IP. Until your ISP does this, you will not be able to access their site. It is nothing wrong on your end. Some ISP update very often (hourly), others can take 72 hours. I read on there that as of this morning RC had their problems resolved and now it's a matter of waiting for all ISP to update their DNS records.

Basically, just have to hang out here with us dead-beats until your ISP updates.

[fishgeeksrus]

Why does it seem weird to me that people are inquiring about reefcentral on reefland?????

[Reefland]

Seems very weird to me too! Oh well, I guess we're all here for bettering the hobby, regardless of which site it used.

[arconom]

Reefland

I love the site

Everyday at night I make the runs

Reef Frontiers
Nano-reef
reefland
Reefs.org
Reef Central
manhattanreefs.com
aqualink

I Chat on RC. But I read on all the others. And window shop

[Reefland]

We are glad that you visit and enjoy your time at Reefland, don't just stop by though, we like to chat too.

[vtec si]

I don't know about you but, I feel lost on RC! They are so big and when I did post a few years back I would get slamed for some of the questions that I would ask. I still check it out from time to time but I DO NOT POST any more.

Martin

[Ninong]

Originally Posted by arconom

I guess alot of people seem to be having this problem Including me. I wonder what happen?

According to gregt, they are having a problem with DNS.

Following are a couple of posts by beerguy that sort of explain things:

Normal DNS propagation is weird. The problem is that some ISPs make their own rules and cache DNS records longer than the record requests. It saves them some network bandwidth but makes changes problematic. Windows has it's own DNS caching issues that doesn't help matters. With no broswer running, open a DOS window and type:

ipconfig /flushdns

Restart your browser and see if it helped. If not, you just need to wait it out.

Second post by beerguy:

DNS is the system that the Internet uses to associate names (like www.reefcentral.com) with addresses (like 198.92.103.99). It's a distributed system, meaning that for things to work properly many (thousands) of systems need to work together to make sure that valid information gets distributed.

DNS uses a number called TTL (time to live) in every record to let servers know how long they should consider the information to be valid. Once the TTL has elapsed the server is supposed to refresh it's information by querying the system that is authoritative for the particular domain; in a perfect world.

Many ISPs have dealt with growth by bypassing the established rules. Instead of referring to TTL information, they cache address information for a specific length of time. This can actually make the end user browsing experience snappier; unless something changes. This is what we're running into. We made some changes, to facilitate future upgrades, and the changes are not being updated properly. While we wish things were different there isn't much we can do but wait it out.

You're welcome to open a ticket with your ISP to try and get them to update their caches.