How to Point a Microsoft Domain to Hostinger Hosting

Objective

Point a domain purchased and managed through Microsoft 365 to a Hostinger hosting plan using an A record, then install WordPress on Hostinger.

Scope and Impact

• Approach uses A/CNAME records only to keep Microsoft 365 email intact.

• Nameservers remain on Microsoft 365. Do not change them.

Prerequisites

• Microsoft 365 Admin Center access with permission to manage Domains.

• Hostinger account access to the target hosting plan (owner or account-sharing).

• The domain name and desired website location/region.

• WordPress admin email, username, and a strong password.

High-Level Flow

• Prepare hosting in Hostinger.

• Get the server IPv4 address from Hostinger.

• Add DNS A record (and www CNAME) in Microsoft 365 Domains.

• Wait for DNS propagation and verify.

• Install WordPress on Hostinger and enable SSL.

Prepare Hostinger

• Log in to Hostinger and switch to the client profile if using Account Sharing.

• Create or select the target website under Websites or Hosting.

• Choose the closest server location to the target audience.

Get Hostinger IP

• In Hostinger, open the hosting control for the target site.

• Locate the server IPv4 address (commonly shown as Server IP or IPv4).

• Copy the IPv4 address for DNS.

Configure DNS in Microsoft 365

• Sign in to Microsoft 365 and open Admin Center.

• Go to Settings > Domains.

• Select the target domain.

• Open DNS records management for the domain.

• Add or update the following records:

• Ensure existing MX, SPF, DKIM, and CNAME records for Microsoft 365 email stay unchanged.

• Save changes.

Verify Propagation

• Allow 5–60 minutes for DNS to begin propagating (up to 24 hours globally).

• Check by visiting the domain and by DNS lookup for the A record pointing to the Hostinger IP.

Install WordPress on Hostinger

• In Hostinger, open the Auto Installer or WordPress setup.

• Select the target domain from the dropdown.

• Enter site title, admin email, username, and password.

• Complete installation and note the wp-admin URL and credentials.

• After DNS resolves, request or enable SSL (Let’s Encrypt) from Hostinger and force HTTPS in WordPress settings.

Post-Setup Tasks

• Log in to WordPress and set Site Address and WordPress Address to HTTPS.

• Install a security plugin and caching plugin if required.

• Confirm email DNS: MX records must still point to Microsoft 365; send and receive a test email.

• Add an A record for any needed subdomains or verify that www works via CNAME.

Troubleshooting

• Domain still not resolving: Confirm the A record value matches the Hostinger IPv4 and there is no conflicting A record for @.

• www not working: Ensure the CNAME for www points to @ and there is no A record for www.

• Email delivery issues: Verify MX records still point to Microsoft 365 and SPF includes Microsoft’s include directive; do not change nameservers.

• SSL not issuing: Wait until A record fully propagates to the Hostinger IP, then reissue SSL.

Handoff Notes Template

• Domain: <yourdomain.com>

• DNS change: A record for @ set to <Hostinger IPv4>, CNAME for www set to @.

• Nameservers: Unchanged (Microsoft 365).

• WordPress: Installed on Hostinger. Admin: <email>, URL: <domain>/wp-admin.

• SSL: Requested/enabled after propagation.

• Email: Microsoft 365 remains active and tested.