A single packet can exhaust the processing capacity of a vulnerable DNS server, effectively disabling the machine, by exploiting a 20-plus-year-old design flaw in the DNSSEC specification.

It's public:

Is github aware that if they just switch the orange cloud on in the ”DNS” section for ”@” and ”www” they get IPv6 automatically?

(Quote)

(Quote)

I run an inbound mail server and secondary DNS server on the VPS and the network and reliability has been better than some other well known providers I use.

* PTR/rDNS Supported

(Quote)

I haven't tried but I think a simple BIND/Tiny DNS based DNS should work fine, again depends upon how many queries is it getting, how many zones etc...

(Quote)

Hello , sorry but here all work good , modify please you DNS https://kinsta.com/blog/safari-cant-establish-a-secure-connection-to-the-server/, problem it's not from us

i just need slave authoritative dns only

(Quote)

Custom Reverse DNS

(Quote)

runs custom kernel alpinelinux with sshd/httpd/dns caching/routing. rock solid with headroom for more

Unsure if they’ve mentioned the process, but I had assumed that they’ll move your VPS over themselves and inform you of the new IP address (before or after), and that you won’t have to manually move t

Brave linux v1.59.120 Chromium: 118.0.5993.88 - no extention was installed, resolv dns: switch and cloudflare

Incoming email is really easy. Install Mailcow, configure DNS, done.

Yesh, and their automation tools are a pleasure to deal with, and it can be tightly integrated with DNS, workers, authentification, etc.