{"id":235,"date":"2026-01-01T02:00:03","date_gmt":"2026-01-01T02:00:03","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=235"},"modified":"2026-08-13T22:37:13","modified_gmt":"2026-08-13T22:37:13","slug":"a-step-by-step-guide-on-how-to-add-domain-to-windows-vps","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/a-step-by-step-guide-on-how-to-add-domain-to-windows-vps\/","title":{"rendered":"Pointing a Domain at Your Windows Server: DNS Records, IIS Host Headers, and HTTPS"},"content":{"rendered":"\n

Pointing a Domain at Windows Server in Four Steps<\/h2>\n\n\n\n

Pointing a domain at a Windows Server VM is a four-step job: create the DNS records, add the site in IIS, bind the host header, and attach a certificate. Each step fails in predictable ways \u2014 wrong record type, cached TTLs, a missing binding \u2014 so this guide shows the exact records and settings to use, from a fresh server to a working https:\/\/yourdomain.com<\/code>.<\/p>\n\n\n\n

Step 1: Decide Where DNS Lives<\/h2>\n\n\n\n

You can manage DNS at your domain registrar (default, fine for most setups), at your hosting provider if they offer a DNS panel, or at a third-party DNS service. For a single domain on one server, the registrar’s DNS panel is sufficient; the plans listed in our Windows VPS comparison table<\/a> note which hosts include their own DNS management panel. What matters is that the records below resolve to your server’s public IPv4 address, so write that address down before you start.<\/p>\n\n\n\n

Step 2: Create the Records<\/h2>\n\n\n\n

In the DNS panel, create these records:<\/p>\n\n\n\n

Type<\/th>Name<\/th>Value<\/th>Purpose<\/th><\/tr><\/thead>
A<\/td>@<\/td>your server’s IPv4<\/td>Resolves the bare domain to your server<\/td><\/tr>
AAAA<\/td>@<\/td>your server’s IPv6<\/td>Optional, only if the host assigns IPv6<\/td><\/tr>
CNAME<\/td>www<\/td>yourdomain.com<\/td>Aliases www to the bare domain<\/td><\/tr>
MX<\/td>@<\/td>mail server hostname<\/td>Only if you run email; never point MX at the VPS otherwise<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Set the TTL to 300\u2013600 seconds (5\u201310 minutes) while you are migrating, then raise it to 3600 or more once everything works. A low TTL during setup means your test machines pick up changes quickly instead of caching a stale IP for an hour.<\/p>\n\n\n\n

Step 3: Add the IIS Site and Host Header<\/h2>\n\n\n\n

Open IIS Manager, right-click Sites<\/strong> and choose Add Website<\/strong>. Give the site a name, point the physical path at your content folder, and under Binding<\/strong> set: Type http<\/code>, IP address All Unassigned<\/code>, Port 80<\/code>, and Host name yourdomain.com<\/code>. Add a second binding with host name www.yourdomain.com<\/code> on the same port.<\/p>\n\n\n\n

The host header is what lets IIS tell requests for yourdomain.com<\/code> apart from requests for any other domain on the same IP. If you skip it, IIS serves the default site for every host name, which is the most common reason “the domain shows the wrong website”.<\/p>\n\n\n\n

Step 4: Add HTTPS<\/h2>\n\n\n\n

Get a certificate for both yourdomain.com<\/code> and www.yourdomain.com<\/code>. The practical options are a free Let’s Encrypt certificate issued and renewed automatically with win-acme, or a commercial certificate from your registrar. Then add a https<\/code> binding on port 443 with the certificate selected and SNI enabled, and use IIS URL Rewrite to redirect all HTTP traffic to HTTPS. If you skip the www binding, visitors to www.yourdomain.com<\/code> will hit a certificate name mismatch.<\/p>\n\n\n\n

Step 5: Verify End to End<\/h2>\n\n\n\n