have you asked enom to add the child namservers, ns1.yourdomain.com and ns2.yourdomain.com to the appropriate ips? (dedicated ips in the vps) and have you set up the A record in the dns zone for the domain?
have you asked enom to add the child namservers, ns1.yourdomain.com and ns2.yourdomain.com to the appropriate ips? (dedicated ips in the vps) and have you set up the A record in the dns zone for the domain?
The "A" record for the domain - that's got me thinking. I didn't yet move the domain itself to the server, only went into Enom to specify the DNS for the domain.
Does the domain itself have to correspond to the IP addresses that I set up for the DNS? Or at least point there? My thinking on this was to first get the ns1.harmonmediagroup.com to resolve and then I could point the actual domain there once that happened. I don't want to point the domain itself to a DNS that doesn't resolve yet - is my thinking correct on that?
Thanks,
CharlesH
Last edited by charlesh; 03-02-2008 at 06:25 PM.
Charles,
The nameservers ns1.harmonmediagroup.com and ns2.harmonmediagroup.com are already registered and point to the correct IP addresses. This can be confirmed at the URL's below:
NS1.HARMONMEDIAGROUP.COM
NS2.HARMONMEDIAGROUP.COM
Therefore you just need to change nameservers at your Domain Registrar Enom to ns1.harmonmediagroup.com and ns2.harmonmediagroup.com. It will take from several hours up to 48 hours until the domain starts resolving to the new server.
Ok, so I guess I wasn't crazy after all. I just tried to ping them and I don't get a reply at all, so that was the only way I was checking to see if it propagated or not. I get a could not find host ns1.harmonmediagroup.com when I try.
Should I be able to ping them at this point or will it take for the actual domain name to transfer? If so, then this thread may help someone else out there when transitioning.
Thanks,
CharlesH