Private IP problem

[Cutia]

Hi,

An existing account wanted upgrading to a secure server account with a unique IP. I assigned the account to an IP rather than the shared IP it was previously on and activated SSL.

For some reason the domain wont resolve any more. I can access it directly using the IP but the nameservers wont direct to it. Have I done something wrong? Can someone walk me through the steps necessary for setting up SSL on an account?

I don't have a certificate yet as I'm waiting for the signing authority to send it.

Thank you.

 

[jmstacey]

You'll want the domain to resolve before moving on.
Make sure that the domain registar has the domain pointing to your nameservers instead of using an A record to point to the old shared server IP address.

Restart named. There have been reports of named not restarting after a change in configuration so it doesn't actually happen until you reload the config files.

If that doesn't work, open the named database file for that domain and make sure the IP in it is correct.

 

[Cutia]

Thank you for your reply. It appears I just needed to be patient. For some reason I expected the domain to resolve immediately to the new IP as the nameservers hadn't changed at all I assumed all resolving would take place on the server. It seems that DNS needed to propagate and all is now well with dnsreport.