[fishgeeksrus]

NO Kidding!!!!! Drama Drama Drama... we are trying to stay under the radar...

Originally Posted by Reefland

Never know with the number of bans occuring over there lately. Sure you didn't post anything that could be construed as "political"?

[Reefland]

I wasn't trying to "crack" on their policies, just sooo many people there to control.

I stay in hiding here at lil'ol Reefland.com.

[fishgeeksrus]

I think they are a little too commercial now...

[Reefland]

All of "us" have went commercial to an extent. All sites reef related require sponsorships to pay for services but they are literally "big business". It's got to be hard to manage...

[Ninong]

Originally Posted by Samper

I haven't been able to get on RC all day. Anyone else experiencing this problem?

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.