(Quote)

(Quote)

The current architecture already separates the admin panel from the user panel. The next phase is multi-server support — a central master node that manages DNS, account provisioning, and migrations ac

DNS, account transfers/migrations to different hardware, administrative management, updates, etc would all be dramatically easier with this configuration.

(Quote)

(Quote)

other things I've noticed, ipv6 only vps but provisioned with only ipv4 dns when you check cat /etc/resolv.conf

Typical flow is: initial sync → TTL lower → final delta sync → DNS switch.

(Quote)

HPanel has a full REST API (Express.js + JWT auth). Every feature in the panel — domains, emails, databases, DNS, SSL, files, backups — has API endpoints. We also have a working WHMCS module for billi

(Quote)

I plan on doing that with DoT eventually, although only for my European servers as that is where most of the exits are. Exits outside of the EU would have too much latency to round-trip DNS there.

If a server does not have ipv6 it's a dealbreaker for me. All my management, backup and internal dns is ipv6 only so it has to be there. Ip4 I can do without, have not really relied on it for the past

IPv4 is slowly fading, though, since I use DNS 99% of the time anyway.

(Quote)

on tmobile by default in newest deployments there is no IPv4 service (no NAT too), you are v6 only + dns servers that will resolve A-only to AAAA into ISP IPv6 space where last two chunks are the v4 a

* DNS servers (even for IPv6 Reverse DNS zones) are IPv4 only (e.g. @chunkserve )

* Outbound mail from ticket system depends on recipient to have IPv4 MX server and IPv4 DNS server (e.g. anyone using @jar MXroute for outbound).

I have been pushing IPv6 for almost two decades. I've made sure even my DNS servers are on IPv6, and TLD name servers had v6 glue.

are then, I would spin up a vps just for dns and it can be used across all the exits.