The domain names in the hands of server enthusiasts are often more numerous than their machines. DNS records are scattered across different providers: free ones might get throttled, shut down, or suddenly add a "for personal use only" clause; the good ones cost dozens or even hundreds of dollars a year. Not to mention if you want traffic splitting by route, DDNS for your router, or automatic certificate renewal—getting all these usually means jumping between three or four different control panels.

So we built our own authoritative DNS and gave it a standalone front: anyns.io. The name is separate, but your account is still the same one you use on N.HT—just log in directly.

1. First, what exactly is it?

It's not a public DNS—it's not the kind you "use for browsing." It's authoritative DNS hosting—point your domain's NS records here, and whenever anyone in the world queries your domain, it answers.

Four independent networks: ns1 to ns4 are on four different network providers, currently with 13 anycast POPs, and more to come. If any one provider fails, the other three keep answering as usual.
You can verify yourself: Don't just take our word for it—dig @ns2.anyns.io yourdomain and see for yourself. The output on the homepage is live.
Permanently free: DNS is a fundamental internet function. Charging personal users for this doesn't make sense, and we don't intend to make money from it.
Leave anytime: All records can be exported as a standard BIND zone file with one click, ready to import to any provider. If you want to leave, you don't need to notify anyone.

2. Traffic splitting: Different answers for the same domain based on source

This is the most "server enthusiast" feature. The same www—visitors from mainland China get a China IP, overseas visitors get an overseas IP, each to their own.

18 preset routes: Mainland China / Hong Kong, Macau, Taiwan / US, Japan, Korea, Singapore + China Telecom / Unicom / Mobile / CERNET + six continents, real traffic splitting by GeoIP and ISP segment—not just for show.
Custom routes: If the presets aren't enough, make your own—build routes with your own IP ranges, up to 10 routes per person, each with 64 CIDRs. Assign a route for your company exit, or a specific data center—anything goes.

3. For machines: the essentials

The panel is for humans to click, but the real workhorses are scripts and routers. So credentials are issued by use case—one key opens only one door:

DDNS: DynDNS2 protocol compatible—just fill in the address on your router firmware, ddclient, or inadyn and it works. Each token is bound to a single hostname—it can only change that one record, so even if leaked, it can't affect anything else.
ACME certificates: DNS-01 automatic issuance and cleanup, acme.sh has a ready-made plugin, lego / Traefik / Caddy use the generic httpreq method—just fill in three environment variables. Wildcard certificates are supported. ACME tokens can only touch _acme-challenge—they can't access your other records.
API: Full CRUD for records, and every command on the docs page can be copied and run directly.

4. A few handy extras

Delegation check: After adding your domain and updating NS, click "Check Now"—it queries the parent zone's authoritative servers directly, zero cache, so you can verify changes immediately without waiting for local recursive cache to expire.
DNSSEC: One-click enable in the panel, get a DS record to paste at your registrar and you're done.
Migrate from other providers: Import zone files directly; for Cloudflare users, you can pull all records in with one click—no need to copy them one by one.

5. CF Cloud: Connect Cloudflare's shield to your own DNS

This is a newly launched feature, and the one I'm personally most excited to talk about.

For domains hosted here, you'll see a cloud icon next to DNS records. Turn it on, and that hostname is routed through Cloudflare's CDN and protection: origin IP hidden, free HTTPS, DDoS protection—while the domain itself stays hosted with us, so you still get traffic splitting, DDNS, API, etc.

It's not magic—it's Cloudflare's official SaaS integration (Custom Hostnames):

Use your own account: In CF, create a restricted token that covers only a "utility domain" and paste it into the panel. The quota is yours (first 100 hostnames are free, after that CF charges $0.10/hostname/month, unrelated to us), the bill is yours—we don't front quota or resell.
We don't touch your traffic: The path is "visitor → CF edge → your origin"—we only call the API for configuration, not in the data path. Wondering if we can see your traffic? We can't—it's structurally impossible.
Fully automated switch: After turning it on, it sets up the origin record, registers the hostname, and issues all ownership and certificate validation records—fully orchestrated, you don't have to do a thing.
No changes to your DNS during validation: This was rebuilt after past pitfalls—before validation passes, DNS still points to your origin, so service is uninterrupted; only when the hostname and certificate are both green does it switch over. The whole process usually takes a few minutes, with no user impact.
One-click revert: The real origin value is always stored in the database—the cloud is just a marker. Turn it off to instantly restore direct connection, no data migration, no half-baked states. Token ciphertext is deleted on unbind.
Traffic splitting records unaffected: The cloud only takes over the default route. If you point the China route to a domestic CDN, it won't touch it.

A few boundaries to clarify:

Wildcard records (*.example.com) can't use the cloud—CF's free plan doesn't support it, and the panel will block it.
You need to enable SaaS on CF's side, which requires entering a payment method (today's due: $0)—that's CF's rule, we can't do it for you. The tutorial page has a five-step illustrated guide.
If you want to use non-443 ports or HTTP origin, you can set it in "Advanced"—the token needs two extra permissions.
We don't do "optimized IPs". Only official methods are supported—CF's terms explicitly forbid proxying domain traffic to non-CF IPs; if detected, the hostname simply fails. The slight latency savings aren't worth risking your domain.

6. By the way, DoH is now included

The DoH encrypted DNS console from the forum is now merged into the same panel. Old access addresses remain unchanged—no need to reconfigure. One account, manage both authoritative and recursive DNS in one place.

7. One line we won't cross

The biggest risk with free stuff is lack of boundaries. So this is written on the trust page and here as well:

Hosted domain targets are continuously checked. No porn, gambling, phishing, or malware domains—confirmed violations will be stopped.
But action only applies to that specific domain—if one domain is stopped, it doesn't affect any other user's records. This is the bottom line—no "guilt by association."

The motivation for building anyns is actually simple: we're people who tinker with domains every day, so we know where the pain points are. Point your domain here, and let it handle the rest of the chores for you.

No matter how much technology evolves, the soul of the community is still every passionate "old hand" and new friend.

I hope to be able to continue doing this steadily over the long term.

Well, the current demand for computing power on the internet is huge. Compared to various other startups, the anyns project is the cheapest way.
I also believe I can stick with it.
Test edit

Wrote so much. The features are pretty good.

Functionality is one aspect. Attracting users is another issue altogether—it's a headache.

Impressive, man. All practical features.

There is still plenty of room for improvement.

This is written so well, deepseek(

MX seems to have some issues, guys. When adding, it keeps saying there's a format problem.

The correct format should be
priority space domain name
For example
I'm using it now too.

10 mail.n.ht

I set it up like this too, but it keeps saying there's a problem. It's best to separate the priority numbers to make troubleshooting and input easier.