Quote from: Rannasha on October 07, 2013, 03:05:38 PM

Quote from: Jere.Jones on October 07, 2013, 03:04:07 PM

Quote from: Rannasha on October 07, 2013, 03:02:58 PM

Quote from: twentyseventy on October 07, 2013, 02:58:09 PM

Quote from: DrGregMulhauser on October 07, 2013, 02:46:07 PM

As far as I can tell, the domain name itself expired yesterday, and the registrar eNom has helpfully decided to cease providing correct DNS information with immediate effect: their service at name-services.com is now returning the IP 8.5.1.36 for btct.co queries instead of the IP 141.101.113.21.

I am not recommending the following, because many people will rightfully expect a signed, sealed, and gold plated confirmation from Ethan before trusting any information about iP addresses, but if you were to place the original IP address in a hosts file, and clear your DNS cache, you would then find that the site is still very much alive and kicking. I have just done this myself and could see the last trade shown on the front page was only 49 seconds ago, so either people with cached DNS information are still able to get there, or the problem was resolved while I was typing.

The registration itself should have a grace period, and abruptly ceasing DNS services for the domain does not, in my view, speak very well at all for eNom.

Thank you for the information. Really wish I hadn't closed that tab, now. Editing my hosts file and flushing the DNS cache isn't working for me - do I put the correct IP address first, then the 8.5.1.36 IP address after that?

In the hosts file, add a line with:

Code:

btct.co 141.101.113.21

and then flush you DNS cache.

Shouldn't it be the other way around?

Code:

141.101.113.21 btct.co

You're correct, it's been a while since I've had to edit my hosts file.

Thanks very much guys, I really appreciate it. What a day.