I created vanity name
servers e.g. ns1.example.com and ns2.example.com that are just maskеа and are pointed to
rackspace free dns service. In other words ns1.example.com points to
dns1.stabletransit.com and ns2.example.com points to
dns2.stabletransit.com(stabletransit.com are rackspace's nameservers). In general it
works fine and I can forward domains to ns1.example.com and they will work correctly and
redirected to dns1.stabletransit.com. However for .no(norway) domains I stumbled into
the following error:
The
nameserver ns1.example.com is not correctly configured. It has the following NS records
in the zone file for somedomain.no:
dns1.stabletransit.com
dns2.stabletransit.com
This does not correspond with the
nameservers you have entered, which are:
ns1.example.com
ns2.example.com
The list you enter must be identical to
the list of NS records returned by each nameserver on the list.
For
.no domains the nameservers must be configured correctly before the delegation can be
completed. Not all ISPs are aware of this. Please contact the administrators of the
nameservers you are trying to use, and ask them to create a valid zone file for
somedomain.no on all the
nameservers.
This is
the error message that I got when I try to point .no domains to my vanity name servers.
I will be thanlful if someone can expain why this happens and how can I fix it. As far
as I understand this is a correct way to mask name servers by creating vanity name
servers, so I'm not sure where I'm
mistaken.
Thanks in advance for any
help!
Answer
This is because the "real" nameserver for
the domain tells that dns1.sabletransit.com
and
dns2.stabletransit.com
are the authoritative nameservers for
this domain. (NS record)
The .no
registry seems to check this.
I don't think
rackspace free dns allows you to change this, so I don't think there's anything you can
do.
Comments
Post a Comment