On 12/09/2012, at 10:27 AM, Mark Jeftovic <[email protected]> wrote:
> I don't understand this, they are saying they will only do this for > domains under their management, implying that this domain isn't. Yes. I am saying that using their GUI, to manage a domain which is managed with them, they limit NS to 1) in-baliwick, defined in a hosts.txt file they control and expose a UI to 2) any NS already in use by you, in any domain, under godaddy control 3) any grandfathered in NS, but I cannot verify if this remains true if you drop them from the record of any domain. > > But you later say, only godaddy can modify the whois record for this > domain, which means godaddy is the registrar of record. yep. > > So you do this through the registrar of the parent domain, godaddy - > what am I not getting? Are they not doing it because you're not actually > using their nameservers? I am attempting to define NS delegation outside of the zone, and not using their NS. > > The only exception I can think of is when you need to create a > nameserver record in the gtld roots for a nameserver that is in some > other ccTLD namespace - many registrars won't do that. > > - mark Yep. I'm learning (fast) that this is understood. its subset of possible NS, restricted to specific values, to avoid some bad behaviour but as a consumer of DNS services, I didn't notice the restriction coming in. A new entrant would be presented with a fait accompli. because of the grandfathering of 'strange' NS in imported WHOIS records, I suspect that many of us won't have noticed. -G _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
