I have a site for which I adjusted the NS records 1-3 to point to Adobe Business Catalyst where the site is hosted now:
domain.nl. ns1.worldsecuresystems.com.
domain.nl. ns2.worldsecuresystems.com.
domain.nl. ns3.worldsecuresystems.com.
I assumed this would be enough to point to the new server with site data. When I did a dig I saw
dig +short SOA domain.nl
ns1.worldsecuresystems.com. hostmaster.domain.nl. 2014071224 14400 3600 1209600 86400
When I checked the site on viewdns.info I got two warnings though:
Oops! Your local nameservers don't return IP addresses (glue) along with your NS records! This isn't a fatal error but means an extra lookup needs to be performed increasing the load time to your site. You can fix this by adding A records for each of the nameservers listed above.
and
Oops! It appears that the following nameserves listed at your local servers are not listed at the parent servers:
ns1.worldsecuresystems.com.
ns2.worldsecuresystems.com.
ns3.worldsecuresystems.com.
You should ensure that these nameservers are valid and working. If they are not, you will encounter connectivity issues with your domain.
And the site is not resolving properly. It is still going to the old hoster's ip (hosted with correcthosting.nl ) where the old site is now.
nslookup domain.nl
Server: x.x.x.x
Address: x.x.x.x#53
Non-authoritative answer:
Name: domain.nl
Address: XXX.xx.xx.xx // old ip address
I do not see a reason why it does not work. I have asked Business Catalyst and the hoster where the domain is at for help a while ago, but will have to wait for answers. If anyone here in the meanwhile has some pointers that would be great.
if your domain is domain.nl, you don't need glue for nameservers ns*.worldsecuresystems.com. Whoever says that you need glue in this situation, is lying to you, unless you are lying about your domain name. DNS doesn't propagate - records expire. Use dig or drill for querying nameserver.
"It appears that the following nameserves listed at your local servers are not listed at the parent servers"
this message is an indication of neglect or failure to delegate authority to the nameservers specified with NS records in your zone. This may be related to the problem with glue records missing, but doesn't explain why glue is considered needed.
the data in SOA record says nothing about authority over zone. delegation records in parent zone do. Seeing that you're using dig already, try dig +trace yourdomain to see delegation chain.
"site is not resolving properly. It is still going to the old hoster"
means it's resolving properly, just not to the ip address you were expecting.
However, ns1.worldsecuresystems.com doesn't consider itself authoritative for domain.nl, which is a sign that the zone domain.nl hasn't been set up on that nameserver.