Did anyone else have to flush their DNS to access the forum today?

[dualstow]

Or was that just me?

I thought something was up right away because the profile pic didn't load, indicating that I was probably looking at a cached copy of the site. Beyond that, I don't know much about caches and computers. Clicking any link led me to a page that this site had moved, along with various DNS-flushing instructions. However, they don't work for the latest Apple operating system, OSX El Capitan.

I found some instructions that do work and would post them here, but anyone who needs them would not be able to click here to get to them! 

[Tyler]

I did as well.  I thought it was a scam at first, but after some research I tried it and it worked.  I still have no idea how to fix my iPad, but I'll worry about that later.

On a positive note, I believe this type of thing naturally resolves itself in 24-72 hours.  http://www.mochasupport.com/kayako/inde ... icleid=227

[Xan]

I'm guessing that MTex upgraded his plan with the host, which involved moving the forum to a different IP address.

There couldn't possibly be a scam; there's no harm in flushing your DNS cache.  I guess the only risk would be following instructions to flush which actually did something else.

Tyler's right that it will fix itself.  The TTL for the domain's A record is 24 hours, so that should be the absolute max time that anything's broken.

I'm a little surprised that the host would post instructions telling web users to flush their DNS cache rather than actually managing the transition so that it never is a problem.  There are certainly ways to do that.

[dualstow]

Immediately after the DNS flush I could not get in, but after I restarted I could. Then, after I started this thread, I got a different kind of error. One that I've seen in the past. Add to that what you two said and I guess I could have just waited. Hmm.

[Libertarian666]

Yes, I had the same problem. I had to restart Firefox after flushing the DNS cache.

[dualstow]

Thanks. Ah, I should have tried restarting the browser first instead of the whole machine.

[mathjak107]

same here , didn't know i had to restart