Knackered domain records

[Chris H]

Decided to switch one of me blogs to blogger as I'm bored of maintaining it. Went to Blogger's instructions regarding changing records so the url loads the blogger stuff.

It said I needed to create a CNAME record for your domain with the DNS, associating your domain with ghs.google.com. However, with 123-reg you can't do this unless the nameservers are ponting to 123's server names. So I created the cname record, both A and WWW and deleted the existing ones and set the nameservers to 123.

Then I remembered I had an adsense site bringing in some cash as a subdomain of the blog. So I reversed everything except that I have no idea what the ip address was for the original dns settings.

Now me page won't load. 

Any advice to get this sorted?

[Mike@TheWhippinpost]

Can't you just ask your old hosting provider?

[Chris H]

I know the nameservers, but I've no idea what ip addy should go in the @ and www dns records.

Not sure if that comes from sitehq or the registrar.

[Jeewhizz]

Put the IP address for the ns1.domain.com nameserver if it's sitehq.

[Chris H]

Done that Jee but the resolved up is different for all the other ip addresses as listed in the dns records for other sites on the same server? 

[Chris H]

Jee, the ip for the sitehq ns1 server is different from the ip address for all the other sites I have on that server as listed in the dns A name records for @ and www.

Is this right?

[Jeewhizz]

If it's on the same server as the other sites, then use the IP on the other DNS records.

[Chris H]

Ta. I'm sure I did that as that's what's reading now.

Unfortunately to reset the dns records I have to change the nameservers to 123-reg and allow that to propogate before I tinker with the dns settings again.

Maybe I didn't leave it long enough.

[Chris H]

OK, what does control how the domain name gets translated into an ip?

Is it in the nameservers or in the CNAME record? Both seem to do the same thing to me.