They did understand but said that function no longer works. I don't know why the UI still exists. To be clear you can add name servers that were already defined to your zones in the root servers but can not create new ones. So I could for example add pdns196.ultradns.org as an authoritative NS for my zones but if I rack mount a server and expose DNS using one of my domains then people will only learn about it when they query my NS records from other DNS servers that are already defined such as ultradns, google, etc... because they already queried NS from pdns196 meaning to your point that one I just provisioned will lack glue records in the root DNS servers.
This has nothing to do with root zones. The root zones tell a resolver where to send the next query to find .org domains, for example. They don’t know about your zone, nor should they.
> pdns196.ultradns.org as an authoritative NS for my zones
Okay, sounds like what most registrars can do. (Although Cloudflare seems to have very odd concepts of what DNS means…)
> but if I rack mount a server and expose DNS using one of my domains
I can’t parse this. Are you saying you have a server with a fixed IP address and it’s running an authoritative DNS server for one of your domains?
> people will only learn about it when they query my NS records from other DNS servers that are already defined such as ultradns, google, etc...
This almost sounds like common recursive resolvers like 8.8.8.8 can find you, which is what you would expect.
> because they already queried NS from pdns196
Queried NS for what domain?
> meaning to your point that one I just provisioned will lack glue records in the root DNS servers.
Of course it lacks glue records in the root servers. It’s the servers for the level in which you are registered that should have the records.
Maybe post the output from dig +trace [domain] and explain how the output differs from what you expect?
OP is running one or more DNS servers, and wants to have "vanity" nameservers for their domain (e.g. ns1/ns2.example.com for example.com, rather than ns1/ns2.theirhostingprovider.net). This is generally inadvisable, but it's their prerogative.
Setting this up typically requires OP to set up glue records at the registry so that the .com (or whatever TLD is applicable) can return IP addresses in the delegation to ns1/ns2.example.com, so that resolvers don't get "stuck" trying to resolve the domain. Typically this is done through the registrar, but apparently NetSol isn't cooperating. I've never heard of a registrar refusing to do this before; I'm not sure it's even permitted by the registrar agreement.
OP is running one or more DNS servers, and wants to have "vanity" nameservers for their domain (e.g. ns1/ns2.example.com for example.com, rather than ns1/ns2.theirhostingprovider.net). This is generally inadvisable, but it's their prerogative.
Eh, since when is having in-bailiwick name servers not advisable? Is it stated in some BCP or draft? In-bailiwick servers and glue records have been standard practice as long as DNS existed.
Adding to this if I am not running my own nameservers I can not watch DNS requests to see how bots are evolving. I sometimes take evasive maneuvers to trip up the bots. Some ... well most ... would say I should be using Cloudflare for such things but I am not even going to write up a blog on why I will not. I run my own servers for anything I can and then my hobby is to play blue team with the bots and skiddies. I can't do that with other peoples nameservers.
