DNS Cutover Guide

Read this first

The domain currently runs live email on a separate mail server (sc161.sgcloudhosting.cloud). Moving the website does not move the mailboxes.

Change only the two records in Step 1. If the MX, SPF, DKIM or the mail / webmail / cpanel / autodiscover records are edited or deleted, email will stop working.

01Change these two records

Log in to Cloudflare, open surveillancezone.com.sg, then go to DNS › Records. These are the only two entries that need editing.

A surveillancezone.com.sg Replace

Name@ (shows as the root domain)

Old value188.114.96.3 / 188.114.97.3

New value46.224.233.157

Proxy statusDNS only (grey cloud, not orange)

TTLAuto

A www.surveillancezone.com.sg Replace

Namewww

Old value188.114.96.3 / 188.114.97.3

New value46.224.233.157

Proxy statusDNS only (grey cloud, not orange)

TTLAuto

If an AAAA record is listed for @ or www

Delete it. An AAAA record is an IPv6 address, and any leftover one would keep sending some visitors to the old host. The IPv6 addresses showing today (2a06:98c1:3121::3) come from Cloudflare's proxy, so they usually disappear on their own once the record is switched to DNS only. If one is still listed after that, remove it.

Why the cloud icon must be grey

The new server issues its own SSL certificate, and it can only do that if the domain points straight at it. Leaving the record proxied (orange) blocks the certificate and the site will show a security warning. Grey cloud, also called DNS only, is required.

02Do not touch these

These are the live email and mail-service records, read from the domain on 25 July 2026. Leave every one of them exactly as it is.

MXsurveillancezone.com.sgKeep

Value0 sc161.sgcloudhosting.cloud

PurposeDelivers all incoming mail. Removing this stops email immediately.

TXTsurveillancezone.com.sg · SPFKeep

Valuev=spf1 +a +mx +ip4:103.7.9.57 include:all._spf.ds.network include:se.mschosting.com -all

PurposeTells other mail servers who may send as this domain. Editing it sends outgoing mail to spam.

TXTdefault._domainkey · DKIMKeep

Valuev=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+1d+G0wxk8BPtdA6vE100lewmRH4rUxA2ydyRTZe41yNiGnekyZKJIlBNNNqvaymwFYbZYIkPTIawzN7aPfuAqvUpETD0WiKnexPCJvJz41SmiWP8qSkcnBRTzk3fLWGjR9lbYgiyTZYMQtAqNyvrDd9m/2mEDq1ggM5P+5A1z1M98qPoP/0us5ySxv3ocQ6Icbnla1yamIU++K66HwPhGrG2UCW0Ppxhh3C8lheEMvKWoSxyGIOLbHYRLPAXu/iheHRLyPui5zYsXDJA9BO4YMNiqZ+ptIdE6lbLE2kgTxOomIJR9oLRtCIraeqlhl82dtzSZtxQs73B53JMtJ14wIDAQAB;

PurposeSigns outgoing mail so it is trusted. Do not regenerate or delete.

Amail · webmailKeep

Value103.7.9.57 (both)

PurposeOutlook and phone mail setup, plus the webmail login page.

Acpanel · autodiscoverKeep

Value18.140.232.254 (both)

PurposeHosting control panel and automatic Outlook account setup.

Aautoconfig · ftpKeep

PurposeMail client auto-setup and file transfer. Not used by the website, so leave them alone.

03The order to do it in

Tell us before making the change
The new server needs the domain registered on it first, which is already done. A quick message means we can watch the switch happen and issue the certificate the moment it lands.
Change the two A records
Root domain and www, both to 46.224.233.157, both set to DNS only. Nothing else.
Wait for it to spread
Usually 5 to 30 minutes on Cloudflare. Email is unaffected during this window because the mail records never changed.
We issue the SSL certificate and complete the cutover
This is our side. Once the domain resolves to the new server we finish it and confirm.
Check it together
Load the site over https, send a test email in and out, and confirm webmail still opens. Then it is done.

04If anything looks wrong

The change is fully reversible. Putting the old values back returns the site to the current host within minutes.

A @ 188.114.96.3 (Proxied) A @ 188.114.97.3 (Proxied) A www 188.114.96.3 (Proxied) A www 188.114.97.3 (Proxied)

Email cannot break from this

Every record that email depends on is untouched by this migration, so a website problem can never take mail down with it.

05Three things worth knowing

Keep the existing hosting plan active. The mailboxes, webmail and control panel all still live on the old host. Cancelling that plan after the website moves would take the email with it. Cancel only after email has been moved separately, if that is ever wanted.
The SPF record contains +a. That means "also allow whatever the website A record points to" to send mail. Right now it points at Cloudflare's proxy, which does nothing useful, and after the move it will point at the new web server. Real mail sending is unaffected either way because +mx and ip4:103.7.9.57 already cover the actual mail server. Tidying up +a is optional and can be done later.
There is no DMARC record on the domain. Not required, and nothing breaks without it, but adding one later improves deliverability and protects the domain from being spoofed. Worth doing as a separate task once the site has moved.