Community group: https://t.me/anyns_nht
09-21 Update: The prefix for branded NS now supports customization, no longer fixed to ns1, ns2. See point 2.

1. Update: Streamlined from 4 entry points to 2 entry points, aligning with the industry-standard CF.

ns1.anyns.io
ns2.anyns.io

(Users of the original ns3 and ns4 can continue to use them, as they also redirect to ns1 and ns2.)
Significantly expanded nodes, scaling up to 25 independent nodes, including 8 cross-IPv6 network nodes and 3 independent IPv6 nodes. Full-line anycast, with IPv6 capability.

1. Today we're not talking about CF acceleration or custom routing. Today we're talking about how to replace ns1.anyns.io and ns2.anyns.io with your own branded NS.
   In the backend at https://anyns.io/panel/brand-ns

Select the custom branded NS domain you want to set up (this domain must first be hosted on anyns and have delegation completed). Here I'll choose my own domain n.ht.
The backend shows the following glue records need to be added:

ns1.n.ht points to (recommended to select at least one IPv4 and one IPv6)
185.187.153.13
185.187.153.14
2a14:1ec7:f7fe:6::13
2a14:1ec7:f7fe:6::14

ns2.n.ht points to (recommended to select at least one IPv4 and one IPv6)
109.224.231.13
109.224.231.14
2a05:b0c4:1::13
2a05:b0c4:1::14

Note: Only legitimate domain registrars can add glue records. Some reseller APIs may not support glue record capability; you can contact customer service via ticket for manual processing.
Some of you may not have encountered glue records before. Actually, glue records are registered at the registry, and are provided by the registry alongside NS records.
For example, when baidu.com's domain hasn't yet had its NS take effect, glue records can already be registered with the registry.
ns1.baidu.com ~ ns4, ns7 point to Baidu's NS servers, so that the domain can find its own NS servers before the NS records take effect, thus solving the chicken-and-egg problem.

After the glue records take effect, all my domains including n.ht can be enabled by clicking "Brand NS" in the top right corner at https://anyns.io/panel/zone/n.ht, then going to the registrar to change the domain's NS to ns1.n.ht and ns2.n.ht, to use as custom branded NS.

1. To give anyns.io users more peace of mind, we've updated the n.ht rules to clarify that n.ht rules do not apply to anyns.io: even if a user is banned on n.ht for violations, it will not affect their use of anyns.io.

Can anyns.io support secondary mode? I run my own domain system, and migrating directly to anyns.io would require too many changes. It would be great if anyns.io could create a secondary zone and pull records from my authoritative server.

There is no secondary mode yet; we are still evaluating the development difficulty. The currently available workaround is: export the zone file in BIND format on your authoritative server, and import it through the anyns panel or the import interface of the management token API.

This way, non-standard adaptation is required, and the maintenance cost is a bit high.

Mainly DNSSEC support, and also the number of your zones. If you want to support DS, it will be more troublesome.

It has little to do with DNSSEC. Because the relevant records are all statically pre-generated (and signed) in advance, they can be synchronized just like ordinary records. There is no need to distinguish whether DNSSEC is present, nor is there any need to set up DNSKEY and other related records on the anyns.io side.

NS mainly involves stability, let's try a few domains to test the waters.

Come on, absolutely stable. My actual job is being responsible for bank operations, and I have relatively high requirements for DNS high availability and resolution stability.
Please feel free to leave DNS to me.

Same here, no wonder your category includes Xinchuang. Hahahaha

Hmm, in today's society, the information technology application innovation ecosystem is basically unavoidable.
Outside this ecosystem, it's becoming increasingly difficult for young people to find IT-related jobs.

I've also recently encountered many problems while helping some students look for jobs.
I can't help but sigh that the skills required for mainstream IT positions are now deeply tied to the information technology application innovation environment.
Some students may not yet realize the problem and still think that not being able to find a job is an issue of the "overall environment."
In fact, it may be that their own direction was detached from the mainstream tech stack from the very beginning.