Comment by duskwuff
2 years ago
I'm going to try to translate a bit.
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.