NSI Not allowing Host registrations for nameservers in sub-zones?
shane at bratnet.net
Thu Dec 5 04:43:32 UTC 2002
My issue is that every time I call NSI to have them help push those
host-forms through, they
tell me that they don't allow nameservers like a.dns.company.com and
b.dns.company.com anymore, you can manage old
records, but you can't request new registrations.
I think that they are on full or it, but every "Supervisor" I talk to there
seems to be spewing the same statement.
Who is NSI to declare my host-records not registerable?
They seem to be saying it as if, Registering a.dns.company.com as a name
server confuses our Online Manegment Software and therfore we are no longer
allowing customers to register hosts like that.
I am looking for some sort of "Authorative" answer, or the RFC# that states
that NSI has NO ability to make that type of host registration choice? And
that they should fix the problem with their software.
Shane Brath wrote:
> I am just looking to find out if I am just missing something or what.
> But several of the reps at NSI that I have talked to have told me
> that they no longer allow registration of name servers in anything other
> than the first level of a zone.
> IE: ns1.company.com and ns2.company.com are OK
> But: ns1.dns.company.com and ns2.dns.company.com are not OK.
> Have I completly missed something, or are the people at NSI just
> jerkn' me around.
> I have tried "without luck" to register several new name servers for my
> that are in a sub-zone, but they are all being rejected.
> Sugestions, other than move the name server names into the zone itself?
>Sr. Lead Software Development
>TDS Telecom, Madison WI.
>shane at bratnet.net
I've never heard of such a thing. register.com doesn't seem to have any
problem with all of our zones (including daimlerchrysler.com) being
delegated to nameservers whose names are in the
More information about the bind-users