(Quote)

Yes, this has now been fully resolved. The remaining symptoms you were seeing were related to DNS (UDP port 53), following the earlier mitigation steps. At this point, DNS resolution should be functio

well, now is reported in status page again as: Los Angeles DC-02 DNS Issue..

marked as resolved 2-3 hours ago, but servers don't work yet... problems with DNS, etc

(Quote)

(Quote)

Can you check the network on your Kemerovo VPS and tell me if it is having any issues? Mine is on 2.59.161.0/24 and can happily access 77.88.8.8 (cdn.yandex.ru) but cannot access 8.8.8.8 (dns.google.c

and change myserver.com's IP to another IP in DNS.

While DNS is gone for now, it may come back in the future as an add-on to WebHosting or similar, before being brought back fully as a standalone product. We would want to make some fairly large change

(Quote)

My domain was added very early on (before the product even launched publicly). It was marked as beta and it was free. Probably Alex meant only one person actually paid for the DNS product. I can't rea

* Domain & DNS management

I'd spent a lot of time thinking about how to roll my own GeoDNS, and then I saw yours that seemed nice and easy to configure and seemed to work from my test.

(Quote)

Honestly, this seems a bit unfair. Yes, the migrations were handled poorly, but you've still got service haven't you? (Honestly, I can't remember, so apologies if you don't). If it's just that you're

(Quote)

DNS was not a main project. It was an additional product that was released alongside our S3 offering as an option if people were interested. While we had over 100 users signed up for the DNS service w

@AlexPads just wondering what's happening with your GeoDNS nowadays.

Let's Encrypt is also working on a longer-term DNS validation method so you don't need to change validation values as often. This won't affect the 6-day IP certificates, because these must use HTTP v

DNS & network tools