Yes. Your main site can remain on its current host while blog.example.com runs on a different server. Create a DNS record for the subdomain that points to the second server, configure that server to accept the hostname and serve WordPress, install a TLS certificate, and set WordPress Address and Site Address to the final HTTPS URL. DNS chooses the destination; it does not configure the web server, PHP, WordPress rewrites, certificates, or redirects.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The safest sequence is to decide between an independent WordPress installation and a Multisite subsite, connect the subdomain, configure the destination server, then test URLs, permalinks, media, login, REST, cron, sitemap, and administrative screens before switching traffic.
As an Amazon Associate I earn from qualifying purchases.
How the arrangement works
A browser requesting https://blog.example.com/post-name/ goes through several separate layers:
- DNS resolution: the authoritative DNS provider returns the address of the second server.
- TLS negotiation: that server presents a certificate covering
blog.example.com. - Virtual-host selection: Apache, Nginx, or a load balancer uses the requested hostname to choose the blog’s site configuration.
- Application handling: the selected document root passes PHP requests to WordPress and applies its rewrite rules.
- WordPress URL generation: WordPress creates canonical links, redirects, media URLs, REST endpoints, login links, and sitemap entries from its configured site URL.
A successful DNS lookup therefore does not prove that the blog is configured. A server with no matching virtual host may show a default site, and a server without the correct rewrite or PHP configuration may return 404 or download PHP files. WordPress’s developer documentation summarizes the requirement as configuring DNS to map the domain to the server’s IP address and configuring the server to map the domain to the WordPress installation directory.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Choose an independent installation or Multisite
Make this decision before changing DNS. It determines who can administer the blog, how updates and backups work, and how difficult a later move will be.
| Decision factor | Separate single-site installation | WordPress Multisite subsite |
|---|---|---|
| Ownership and administration | The blog has its own administrators, dashboard, configuration, and operational schedule. | The blog belongs to one network and is governed by a network administrator as well as any site administrators. |
| Core, plugins, and themes | Core, plugins, and themes can be selected and updated independently on the second server. | WordPress core files are shared. Plugins and themes are managed within network rules; a network administrator may need to install, update, or enable them. |
| Database and media boundaries | Uses its own database and uploads area, making ownership and restoration boundaries clear. | Each site has separate database tables and media directories, but the network shares the installation and administrative model. Sites do not automatically share posts, pages, or other content. |
| Backups and updates | Back up and update the blog on its own schedule and restore it without affecting the main site. | Backups and updates must account for the whole network and every mapped site. |
| DNS and hostname work | Only the blog hostname must reach the new server. | The mapped subdomain must reach the network, and additional sites may require additional mappings or wildcard DNS. |
| Migration and rollback | Moving the blog or reverting DNS is usually more contained. | Changing a network’s addresses requires checking every stored site address, rewrite rule, cookie scope, and mapped hostname. |
Choose a separate installation when the blog is independently owned, hosted, backed up, updated, or likely to move. Choose Multisite when it is intentionally one site in a centrally administered network that benefits from shared core files and network administration. Multisite is not a content-sharing shortcut: posts and media remain site-specific unless you deliberately build integrations.
Pick the right DNS record
Add the record at the DNS provider that is authoritative for example.com. Do not add it only at the registrar if the domain’s nameservers point elsewhere.
| Record | Use it when | What to verify |
|---|---|---|
| A | The second server has a stable public IPv4 address. | Confirm the address will not change unexpectedly and that firewalls allow HTTP and HTTPS traffic. |
| CNAME | The hosting or platform provider gives you a hostname and supports using it as the target. | Use the provider’s exact target hostname. A CNAME cannot normally coexist with other records at the same name, and some providers do not permit it at an apex name. |
| Wildcard | Several subdomains, not just the blog, should resolve to the same destination. | Understand the operational blast radius: an unplanned subdomain may reach the new server. The WordPress documentation gives the example *.example.com A 192.0.2.1 and an Apache ServerAlias *.example.com. |
For one blog, an explicit blog A record or provider-supported CNAME is easier to audit than a wildcard. A wildcard is useful for a Multisite network that creates many subdomains, but it does not replace individual site configuration, certificates, or WordPress address mapping.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
End-to-end setup procedure
1. Prepare the destination server
- Provision a stable public endpoint and record its IPv4 address or provider hostname.
- Install a supported web server, PHP runtime, and database, or use a managed WordPress environment that supplies them.
- Upload or install WordPress in a dedicated document root, such as a directory reserved for the blog rather than the server’s default site.
- Open the firewall for TCP ports 80 and 443 if the server is directly exposed. If a load balancer or proxy is used, allow its documented origin traffic instead.
- Take a backup of any existing WordPress files and database before changing their URLs or moving them.
2. Create the DNS record
Create blog.example.com as an A record for a stable IP or as a CNAME to the provider-supplied hostname. Leave the main domain’s existing records unchanged. Save the change, wait for caches to expire, and verify it from more than one resolver rather than relying on one local result.
dig blog.example.com A
dig blog.example.com CNAME
nslookup blog.example.comThe returned answer should be the new server or the intended provider hostname. If one resolver still returns the old host, propagation or a conflicting record is the issue; changing WordPress before resolution is consistent will only make diagnosis harder.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Configure the web server’s hostname and document root
The destination must explicitly accept the subdomain. Add blog.example.com to the virtual host or Nginx server_name, point it at the WordPress document root, enable PHP handling, and apply the WordPress front-controller rewrite.
A minimal Apache shape is:
<VirtualHost *:80>
ServerName blog.example.com
DocumentRoot /var/www/blog
<Directory /var/www/blog>
AllowOverride All
Require all granted
</Directory>
</VirtualHost>A corresponding Nginx shape is:
server {
listen 80;
server_name blog.example.com;
root /var/www/blog;
index index.php index.html;
location / {
try_files $uri $uri/ /index.php?$args;
}
}These are structural examples, not complete production configurations. Your PHP-FPM socket, permissions, security headers, logging, and distribution-specific include files must match the server. Test that the hostname serves this WordPress directory rather than a default virtual host before proceeding.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
4. Install TLS and choose the final URL
Obtain a certificate that covers blog.example.com. A wildcard certificate may cover multiple subdomains, but its scope should match your security policy. Configure the HTTPS virtual host, then redirect HTTP requests to HTTPS.
In the WordPress dashboard, open Settings > General and set both WordPress Address (URL) and Site Address (URL) to https://blog.example.com, unless WordPress core is intentionally installed in a separate directory. Do not leave one field on the old hostname or on HTTP. If you cannot reach the dashboard after a URL change, use a controlled configuration or database recovery procedure and restore the backup rather than repeatedly editing values.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems5. Configure a reverse proxy or CDN, if present
A proxy is optional. If one sits between visitors and the WordPress server, it must pass the original Host and scheme, normally through the host and forwarded-protocol headers. WordPress’s reverse-proxy FAQ explains that a proxy which overwrites HTTP_HOST can produce wrong links and redirect loops; where necessary, configure WordPress to use the documented HTTP_X_FORWARDED_HOST or SERVER_NAME value.
Make the proxy’s HTTPS-to-origin behavior explicit. If visitors use HTTPS but the origin sees HTTP, WordPress may emit insecure URLs or redirect every request. Configure one canonical redirect layer, confirm the origin trusts forwarded headers only from the proxy, and do not allow arbitrary clients to spoof them.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
6. Set permissions and rewrite behavior
The web-server account must be able to read WordPress files and write only where WordPress needs to write, such as the uploads directory and selected cache directories. Ensure the rewrite module or Nginx equivalent is active. Visit a pretty permalink, not just the homepage, and verify that the request reaches WordPress instead of returning a web-server 404.
7. Connect an existing blog carefully
If the blog already exists elsewhere, export or copy its files and database, then restore them on the destination before changing public DNS. Back up both first. Update stored site addresses from the old hostname to the subdomain with a tool that understands serialized WordPress data; a plain text replacement can corrupt serialized values. Check attachment URLs, menus, widgets, custom fields, canonical settings, and any hard-coded references in themes or plugins.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a Multisite migration, update the stored addresses for every mapped site and inspect the network’s rewrite configuration. WordPress warns that changing SUBDOMAIN_INSTALL and rewrite rules alone does not migrate existing site addresses or configure DNS, virtual hosts, TLS certificates, redirects, and cookies.
8. Verify before announcing the move
Use a temporary hosts-file entry or an origin-only hostname when you need to test the new server before public DNS is changed. Once DNS points to it, perform the following checks in an incognito browser and with command-line requests:
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
- The HTTP URL redirects once to the HTTPS subdomain, with no loop.
- The homepage, a category, a post, a search result, and a deliberately nonexistent URL behave correctly.
- Permalinks work after saving the structure under Settings > Permalinks.
- Images, responsive media sizes, downloads, and any uploaded files use the subdomain and load over HTTPS.
- Login, logout, password reset, and the dashboard work without returning to the old host.
- REST API requests, the block editor, XML or HTML sitemaps, feeds, and canonical tags contain the intended hostname.
- Scheduled tasks and external callbacks still reach the new server.
- Browser cookies are scoped as intended and do not collide with another application on the parent domain.
- Logs show the expected host, client protocol, PHP status, and absence of repeated redirect or permission errors.
Multisite-specific requirements
For a subdomain-based network, the network’s domain must already resolve to the server and the server must accept the relevant hostnames. WordPress’s domain-mapping guidance says the domains you want to use should already be mapped to your DNS server. A wildcard DNS record can send many subdomains to the same network, but you still need matching server configuration, certificates, and site records.
When creating or mapping the blog, distinguish the network’s primary domain from the site’s public domain. Check the network settings, each site’s domain and path, upload locations, and any domain-mapping plugin or proxy rules. A network administrator should test every mapped site after the change because a broad rewrite or cookie rule can affect sites that were not part of the move.
Common failures and precise fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| DNS still shows the old server | Propagation, a conflicting record, or editing a non-authoritative DNS zone. | Check the domain’s authoritative nameservers, remove conflicting records, and query more than one resolver. |
| The new hostname displays another site | No matching virtual host or incorrect document root. | Add the exact subdomain to ServerName or server_name, enable that site, and verify the root directory. |
| HTTPS redirects loop | The proxy terminates TLS but the origin believes the request is HTTP, or two layers issue competing redirects. | Preserve the original scheme, configure trusted forwarded headers, and leave one canonical redirect policy. |
| Homepage works but posts return 404 | WordPress rewrite handling is disabled or .htaccess is not being read. |
Enable Apache overrides and rewrite rules, or add the equivalent Nginx front-controller rule; then resave permalinks. |
| Images use the old hostname or mixed content appears | Old URLs remain in database fields, cached HTML, or theme/plugin settings. | Perform a serialized-data-safe URL replacement, clear caches, regenerate affected content, and inspect source HTML. |
| Login returns to the wrong host or loops | WordPress URL fields, proxy host headers, or cookie scope are inconsistent. | Make both URL fields, forwarded host handling, and HTTPS detection agree; clear old cookies and retest. |
| REST or editor requests fail | Proxy rules, CORS policy, mixed schemes, or a security layer blocking /wp-json/. |
Inspect browser network errors and server logs, allow the required paths, and keep host and scheme consistent. |
| Unintended subdomains reach the blog | A wildcard record or wildcard server alias is broader than intended. | Use an explicit blog record and hostname, or document and secure every wildcard destination. |
| One Multisite site works while another breaks | Only one mapped address was updated, or network rewrite and cookie settings are incomplete. | Review every site’s stored domain and path, certificate coverage, DNS, and network rules before changing individual content. |
Operational practices after launch
- Backups: keep tested copies of the database, WordPress files, uploads, and server configuration. For a separate install, document its independent restore process; for Multisite, test a network-aware restore.
- Certificate renewal: monitor renewal and verify that the certificate still covers the exact subdomain after any proxy or DNS change.
- DNS change control: record the authoritative provider, record type, target, and intended rollback value. Reverting the subdomain record is the fastest DNS rollback, but cached answers mean it is not instantaneous everywhere.
- Monitoring: check the homepage, a representative permalink, login, REST endpoint, certificate expiry, and HTTP status from outside the destination network.
- Updates: a separate site can follow its own maintenance window. A Multisite update may affect every site in the network, so test plugins and themes against the network before enabling them.
- Security: restrict administrative access, keep PHP and WordPress current, use least-privilege file permissions, and ensure the origin cannot be reached with an untrusted forwarded host or protocol header.
When a reverse proxy is worth adding
You do not need a reverse proxy merely because the blog is on another server. DNS plus a correctly configured origin is sufficient. A proxy becomes useful when you need centralized TLS, caching, web-application filtering, traffic distribution, or a stable public endpoint while the origin changes.
It also adds another failure domain. The proxy, DNS, certificate, forwarded headers, cache rules, and origin firewall must all agree. Bypass the cache for logged-in and administrative requests unless you have deliberately designed otherwise, purge cached pages after URL or content changes, and keep an origin test path for troubleshooting. Never use proxy caching as a substitute for WordPress backups.
Quick Recap
Practical decision checklist
- Is the blog independently owned and maintained? Use a separate installation.
- Must it share one network administrator, core files, and update policy? Consider Multisite.
- Does the destination have a stable IP? Use an A record; otherwise use the provider-supported CNAME.
- Do many subdomains intentionally share one destination? A wildcard can simplify DNS, but review its certificate and security scope.
- Have you configured the hostname, document root, PHP, rewrites, and TLS on the destination?
- Do both WordPress URL fields use the final HTTPS subdomain?
- If a proxy exists, does it preserve the original host and scheme?
- Have you backed up files and databases and tested rollback before changing an existing site’s URLs?
- Have you tested permalinks, media, login, cookies, REST, cron, sitemaps, canonical redirects, and all mapped Multisite sites?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
