Update on the pool downtime

Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Update on the pool downtime

by Steve Sokolowski · · Post #6706

edonkey wrote:I can see the main site now.

Looks like there's a tweet that I didn't see rcommending purging the DNS cache. I didn't see that before.

Maybe my problem earlier was a stale DNS entry?

Anyway, looks like you guys are back. Good work! I know that this stuff is hard.
I think that some services don't update their DNS servers very frequently. Westhash, for example, is caching outdated DNS information. Unfortunately, you can't do much about that except wait until their DNS updates.

DNS propagates across the Internet slowly, so even if you clear your cache, the servers might have outdated information still.
edonkey
Archived posts: 11
Joined: Aug 27, 2015

Re: Update on the pool downtime

by edonkey · · Post #6707

Steve Sokolowski wrote:
edonkey wrote:I can see the main site now.

Looks like there's a tweet that I didn't see rcommending purging the DNS cache. I didn't see that before.

Maybe my problem earlier was a stale DNS entry?

Anyway, looks like you guys are back. Good work! I know that this stuff is hard.
I think that some services don't update their DNS servers very frequently. Westhash, for example, is caching outdated DNS information. Unfortunately, you can't do much about that except wait until their DNS updates.

DNS propagates across the Internet slowly, so even if you clear your cache, the servers might have outdated information still.
True. Since I was still seeing problems with my miners connecting, I decided to just use the IP address (192.3.198.21) for now.

I'll change it back when DNS has settled out. I've heard it can take 24 hours to propagate around the world, although usually it seems to happen faster than that (from an anecdotal standpoint).
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Update on the pool downtime

by Steve Sokolowski · · Post #6743

This will be my final post in this thread.

These attacks have been successfully mitigated. They might try again, but they will need to spend a lot more money to succeed. There have been outages lasting about 2s before the measures kick in and drop all the attack traffic. Javapipe's customer service is exceptional and I highly recommend them. I'll be writing a post detailing the full measures that we took and the steps we used to get past the attacks.

Any current issues are not related to the attacks. There are a few issues that came up because we had to release untested code to fix them, and we are repairing those issues. There are also some new performance issues that were uncovered after we fixed the database performance last week - this time it's with WAMP, which we hope to improve this weekend.

If you think that something isn't working, please contact Chris using the information on the contact page and he will investigate the issue. Thanks for your patience during this trying time!