Here's what I need:
- www. and root of domain are hosted on the old host
- beta. is hosted by the new host
Here is the problem:
- Old Host does not allow ANY editing of DNS Records on their Name Servers.
- New Host allows Records to be changed, but you cannot modify A records for root or www.
- I am trying to use the registrar (Network Solutions) who has full managed DNS.
Each host's name servers are already set up to host the root or sub-domain (respectively). Both are shared hosting environments, so I don't think I can use A records. I believe I have to direct different requests, depending on what subdomain is requested, through different secondary name servers.
My imagined solution is to use CNAMEs so that...
- mysite.org and www.mysite.org resolve through ns1.oldhost.com and ns2.oldhost.com
- beta.mysite.org resolves through ns1.newhost.net and ns2.newhost.net
In other words...
mysite.org CNAME ns1.oldhost.com
beta.mysite.org CNAME ns1.newhost.net
Will this work? Is there a better option?
Am I wrong about not being able to use A records? If you set an A record for a domain to resolve to an IP and the hosting environment is shared, does that work? Does the Apache server at that IP know which site on it to show this way?
Answer
You can not use in NS hostnames, which are CNAMEd lately on route (can't recall RFC-number, but it's prohibited on this level)
Both are shared hosting environments, so I don't think I can use A records
But you can do it:
>nslookup www.lazybadger.net
Non-authoritative answer:
Name: www.lazybadger.ru
Address: 188.120.246.161
Aliases: www.lazybadger.net
net cnamed to ru, ru have A
Instead of using such strange DNS-hoster, why not use any independent reliably 3-rd party solution without idiotic limitation? I, personally, have my sites on two different hosters and manage zones independently without any headache
No comments:
Post a Comment