These threats never even come close to the tbps claims. Usually it's just DNS amplification attacks.

DNS is one of those things that's hard to make redundant due to how registrars work, so a single vendor has to do it on our behalf.

Sad to see them shut down. They are/were a good provider and it is becoming increasingly difficult to have diversity in DNS (outside of CF and the big cloud providers).

In case anyone uses Zilore for DNS and missed the email announcement.

can manually resolve by some tinkering in the DNS zones, Haven't tried VPS yet but plan to (although he's receiving good feedback here on those too)

* Reverse DNS Configuration: Yes

my use case is only personal vpn. but some people maybe use it for dns server also.

It will be used as DNS server for my domains.

hmmm... must be a cloudflare / DNS thing?

Lol, anyone know what that's referring to? Their DNS still points at Cloudflare.

Custom Reverse DNS

Have you heard of DNS? You're not really supposed/expected to be remembering regularly used IP's by IP interactively (automate or use DNS).

(Quote)

You should also plan for DNS lookups or you'll expose the VPS activity, which you generally want to avoid when you're deploying a VPN.

(Quote)

need DNS for access to github

(Quote)

IIRC, your reverse DNS is automatically set to the domain vultrusercontent.com. Does this mean that my website content now belongs to you as well?

auto loiface lo inet loopbackallow-hotplug ens18iface ens18 inet static address 192.168.1.2/24 gateway 192.168.1.1 dns-nameservers 8.8.8.8 8.8.4.4iface ens18 inet6 static address prefix::4

(Quote)