Yes, you can set up your own authoritative nameserver.
Yes, you can set up your own authoritative nameserver.
On ns1.example.com and ns2.example.com there are advantages such as improved performance and control. Risks include potential downtime or configuration issues. Changing from a Cloudflare free plan to your own would mean losing access to their features and support.
You’re looking for a straightforward local DNS setup. It should work with tools like nginx proxy manager and your current DNS provider (I use Pihole). Point the cname records to your proxy manager so requests to ns1.example.com are routed through it. This method is effective only within your LAN, but you can connect via VPN for remote access. When you’re not at home, your devices still get DNS from your local Pihole and can reach internal services. If you need a fully public name server, that option doesn’t exist.
Sure to succeed? Absolutely. Anything can happen. But it'll be a steep climb. At the summit, you'll discover instead of open skies and stunning views, more peaks waiting to be tackled. It's a continuous ascent. If you could somehow avoid getting your IP blocked by every upstream NS while maintaining accurate records, and you stayed focused on keeping lookups snappy, you'd likely have a server running roughly half a terabyte of SQL database on RAM-only storage with a 1Gb connection dedicated to freshness. Expect some surveillance—port scanning is probably happening. Stay ahead with regular security patches and scans for intruders. Maybe a bit better security is possible? Some DNS providers track users and sell data, but it seems Cloudflare doesn't. So... nothing. And if you're just handling one site, you'll probably face higher latency compared to other services. TL;DR: Don't attempt this. It's a lot of effort with no payoff.
This depends on your goals. To appear authoritative you must control the domain(s) hosted by your server. For other domains, your DNS provider is usually non-authoritative. Can you manage it? Yes. Should you try? Probably not unless you fully grasp the process. A key point is having at least two servers in different locations for backup. The main risk is someone could compromise your service and mislead users. For instance, redirecting traffic to a malicious IP controlled by an external party. You might find guidance here: ~edit – for personal use, tools like Pi-hole can work well. They often improve DNS speed and are easier to maintain. The downside is you’ll be responsible for keeping them up to date.