You just signed up. The welcome email is in your inbox, the control panel is waiting, and you are not entirely sure what to do first. This article walks through the sequence we recommend for the first 24 hours on Omega Digital so your site is live, your email is delivering, and your certificates are valid by tomorrow.
What you receive at signup
After payment clears, two emails arrive within a few minutes. The first confirms your account and contains a link to the billing portal. The second is the hosting welcome email, which includes your cPanel hostname, a temporary password, your assigned nameservers, and the server IP address. Keep that second email. It has everything you need to connect.
- · cPanel login URL (typically https://your-server.omdigital.cc:2083)
- · Initial cPanel username and temporary password
- · Assigned nameservers, for example ns1.omdigital.cc and ns2.omdigital.cc
- · Primary IP address (IPv4) and, on eligible plans, an IPv6 address
- · FTP, SSH, and database endpoints
Hour 1: secure the account
Before anything else, log into the billing portal and enable two-factor authentication. Use an authenticator app such as 1Password, Authy, or Google Authenticator. Avoid SMS, which can be SIM-swapped. Then log into cPanel and rotate the temporary password to one generated by your password manager. Never email a cPanel password to a colleague; use the portal's user-management features to issue them their own credentials with scoped permissions.
Hours 2–4: point your domain
Your site is not reachable until DNS points to Omega Digital. You have two clean options:
- 01. Change your domain's nameservers at your registrar to the two nameservers listed in your welcome email. This delegates all DNS to us and lets you manage records from cPanel.
- 02. Leave nameservers where they are and add an A record (@ and www) pointing to your server IP. This is useful if you already manage DNS at Cloudflare, Route 53, or elsewhere.
Either approach works. We cover the tradeoffs in detail in the DNS articles below.
# Confirm nameservers have switched (once propagation starts)
dig +short NS yourdomain.com
# Confirm A record resolves to the Omega Digital IP
dig +short A yourdomain.comHours 4–8: install your site and issue SSL
Once DNS resolves to us, install your application. For WordPress, use the one-click installer under cPanel → Softaculous. For static sites or custom PHP, upload via File Manager or SFTP into public_html. Then enable SSL under cPanel → SSL/TLS Status and click AutoSSL. Let's Encrypt certificates issue within a minute once DNS has propagated.
AutoSSL validates ownership by HTTP. Do not enable a full-redirect-to-www rule in .htaccess until after the first certificate has issued, or validation will bounce and fail.
Hours 8–12: create email accounts
Create your first mailbox under cPanel → Email Accounts. Use a long generated password. Add the mailbox to your mail client using IMAP on port 993 with SSL, and SMTP on port 465 with SSL. If you intend to use Google Workspace or Zoho, skip creating cPanel mailboxes entirely and instead configure MX records pointing at the external provider.
Hours 12–24: verify deliverability
Send a test email to a personal Gmail, Outlook, and Yahoo address. Check the headers for PASS on SPF, DKIM, and DMARC. If any fails, fix them before you have real customers on the domain. The deliverability article below walks through it.
Common gotchas
- · Cached DNS. Your computer may show old records for up to 24 hours. Always test with dig or an external tool like whatsmydns.net, never with a browser you've used before.
- · Mixed nameservers. Having some records at one registrar and some at another is a recipe for subtle, difficult bugs. Pick one DNS host and stay there.
- · Skipping 2FA. Almost every account-takeover incident we see starts with a reused password. Enable 2FA on day one.
- · Forgetting www. Most visitors type example.com, not www.example.com. Add both as A records or use a CNAME from www to root.
Still stuck?
Email [email protected] and we will walk through it with you.