Before you take their site live
Confirm, is the client using a Domain Email?
If so, the appropriate MX Records MUST be in place. Otherwise, their emails will fail to send and received.
MX stands for mail exchanger. MX records specify the mail server that will receive and send emails through your domain.
This record is required to be set up if you wish to continue receiving emails at your domain. Generally, we can copy the records from the previous name servers but only before the switch.
Applying MX Records
You can Select and Apply MX records from MCP. MCP -> Server Settings -> DNS Records dropdown. Select the appropriate service and save the page.
The best way to know which service to select is to just ask the client.
SYNC DNS Settings
Whether or not the client has MX records to apply, we must still sync the DNS settings from MCP, into AWS, so that all new records are pushed to the internet.
Search for your target site in MCP, click the checkbox next to it, and select Syncdns SSL from the dropdown and click Go.
This process will Sync the DNS records (and MX Records if applicable) to our AWS public interface. This is pretty much saying that we're hosting the site. The SSL component is also applied, allowing for HTTPS instead of the unsecured HTTP.
This step must be done if any DNS or MX changes are made in MCP, as the settings are not publically applied until the Sync happens.
Pushing a site live consists of setting the site's nameservers to ours:
- ns1.rgnameserver.com
- ns2.rgnameserver.com
- ns3.rgnameserver.com
- ns4.rgnameserver.com
How do they change their name servers?
Changing name servers is something the client must do to take their site live. This must be done through their domain registrar.
Here are a few guides for common registrars:
Extra Info
For changing Domain Names - https://support.realgeeks.com/hc/en-us/articles/219137097-Changing-Domain-Names
The general order for this task would be MX Records (Optional) -> Nameservers -> SyncDNS SLL -> 2-Way Test Email
However, this task order is not strict. All components must be completed in order for the site to be fully functional online. You're able to sync before Nameservers are in place. Which is preferable for MX Records to allow for minimal email downtime once their nameservers are changed.