Subdomains were not moved?

[RFH Reseller: Jaro]

For one of my clients I moved a domain to the RFH server by having the name servers of the domain changed to the name servers as provided in Helm. When connecting to the domain using www.domainname.extension, the page as hosted by RFH is displayed, so this is works as expected.

However, when I try them using a browser, all subdomains (mail., webmail., cp. and subdomains I created) are (still) referring to the subdomains of the previous server the domain was hosted on (i.e. the webmail client of the previous host is displayed) or are unavailable (the latter applies to cp. and the new subdomains I created).

The move took place several weeks ago, so I would expect all DNS changes to be synchronised by now. It concerns a .to domain.

What can cause this behaviour?

[Staff: Warren Ashcroft]

PM me your domain and I will run a few DNS tests - I will post the results here.

[Staff: Warren Ashcroft]

Thanks for the PM - the reason the domain isnt working correctly is due to it not being pointed to our nameservers:

http://www.dnsreport.com/tools/dnsreport.ch?domain=YOURDOMAINHERE

Your NS records at the parent servers are:
ns1.netwerknet.nl. [62.197.129.19 (NO GLUE)] [NL]
ns1.effectus-hosting.com. [62.197.129.19 (NO GLUE)] [NL]
ns2.netwerknet.nl. [62.197.129.20 (NO GLUE)] [NL]
ns2.effectus-hosting.com. [62.197.129.20 (NO GLUE)] [NL]

As a reseller, these should be:
ns1.realnameservers.com
ns2...
ns3...
ns4...

[RFH Reseller: Jaro]

Hi Warren,

Thanks for your fast response. What I don't understand is that the www.domainname.extension works, but subdomains don't. I have my own name server aliases registered with RFH and they have been assigned on NS level (as results from the dnsreport), but not at parent level. I will check this out.

Thanks!

[Staff: Warren Ashcroft]

Hi Warren,

Thanks for your fast response. What I don't understand is that the www.domainname.extension works, but subdomains don't. I have my own name server aliases registered with RFH and they have been assigned on NS level (as results from the dnsreport), but not at parent level. I will check this out.

Thanks!

The reason for that is that www.domain.com (with the Red Fox Hosting IP Address) has been added to the nameservers the domain currently points to.