Let's say I have a main domain xxx.com
and due to migration that host is going offline end of April, now what I have done is, I have registered a new domain account xxx.net
and have xxx.com
forwarded to it which works well.
We however want the .com
to be our main domain, i.e. can I leave the forwarding in place while I change .com
domain's @
record to point to the .net
server and will it propagate in "the background" and once that's completed I'll turn off the forwarding to .net
. Or how else can I achieve that without rendering the .com
unreachable?
This will all happen on GoDaddy servers.
EDIT 1(in reply to Rob-d's ANSWER #1)
Okay, so currently for the .net
domain, I have NS39.DOMAINCONTROL.COM
and NS40.DOMAINCONTROL.COM
as nameservers where for the.com
domain, I have NS07.DOMAINCONTROL.COM
and NS08.DOMAINCONTROL.COM
. What you are saying is, that my .com
URL needs to point to the same nameservers as the .net
URL, is that correct? Can I change this without the domain becoming unreachable?
Thanks!
EDIT 2 (in reply to Chrono124's ANSWER #2)
Thank you, well I'm using Linux hosting with GoDaddy and if my server was different than Apache, I would be surprised. Now since currently both URLs .com
abd .net
that is, refer to different IPs in the zone file, I imagine I should be fine to just sync them up.
What concerns me is that when I enter the IP in my browser, I don't actually get to the website, http://97.74.215.143/ (.com
) and http://97.74.215.143/ (.net
). And for the hosting account, I get:
Nameservers
ns07.domaincontrol.com
ns08.domaincontrol.com
A Record(s)
97.74.215.143
(Your site is Live)
for .com
and
Nameservers
NS39.DOMAINCONTROL.COM
NS40.DOMAINCONTROL.COM
A Record(s)
23.229.134.198
Your site is Live)
for .net