iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Yes—you can keep example.com on its current host while running WordPress at blog.example.com on a completely different server. Create a DNS record for the subdomain, configure the second server to answer for that hostname, install TLS, and set WordPress to use the final HTTPS address. DNS chooses the server; it does not configure the web server, PHP, WordPress rewrites, certificates, or redirects.
The safest deployment sequence is to decide between an independent WordPress installation and Multisite, point the subdomain, configure the destination server, set the canonical URL, then test every public and administrative path before switching visitors over.
How the arrangement works
When a visitor requests https://blog.example.com/article/, several separate systems are involved:
- The visitor’s resolver asks the authoritative DNS service for
blog.example.com. - The returned A or CNAME record directs the connection to the second host.
- The destination web server selects a virtual host or Nginx server block whose hostname is
blog.example.com. - That virtual host serves the WordPress document root, passes PHP files to PHP-FPM or another PHP handler, and applies the WordPress rewrite rules.
- WordPress generates links, redirects, cookies, REST responses, media URLs, and canonical tags using its configured site URL.
The main domain’s DNS records do not need to move. Only the record for the new subdomain changes. WordPress 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 site or Multisite first
This decision affects ownership, backups, updates, and how difficult it is to reverse the change. DNS works with either architecture.
| Consideration | Separate single-site installation | WordPress Multisite |
|---|---|---|
| Best fit | A blog managed, hosted, backed up, or owned independently from the main site. | A blog intentionally operated as one site in a shared WordPress network. |
| Administration | Its own administrator accounts, dashboard, settings, update schedule, and operational policies. | Network administration controls shared infrastructure; site administrators have narrower permissions. |
| Themes and plugins | Can install and update plugins and themes without affecting another WordPress installation. | Core files, plugins, and themes are shared by the network; activation and compatibility can affect other sites. |
| Database and media | Independent database and uploads directory, making selective backup and migration straightforward. | Each site has separate tables and media directories, but the installation and network database remain coupled. |
| Updates | Updated on its own schedule by the team responsible for the blog. | Network-level updates must be planned for every site that uses the shared code. |
| DNS and hostname work | Only blog.example.com needs to resolve to the blog server. |
Subdomain networks commonly require wildcard DNS and matching server aliases; mapped domains add more certificate and routing work. |
| Migration or rollback | Move or restore the blog without taking the main site’s WordPress installation with it. | More tightly coupled; changing network settings or moving one site requires care with stored addresses and network tables. |
Choose a separate installation when the blog may later move to another owner, host, backup system, or release schedule. Choose Multisite only when shared governance and shared code are deliberate requirements. A Multisite subdomain setting by itself does not create DNS records, virtual hosts, TLS certificates, redirects, or migrated site addresses.
Select the DNS record
| Record | Use it when | Example | Important limitation |
|---|---|---|---|
| A | The destination has a stable public IPv4 address. | blog.example.com A 203.0.113.10 |
If the address changes, update DNS before visitors can reach the new server. |
| CNAME | Your DNS provider and hosting provider support an alias to a stable hostname. | blog.example.com CNAME wordpress-host.example.net |
The target hostname must remain valid; a CNAME cannot be used where another record type already occupies the same name. |
| Wildcard | Multiple subdomains should resolve to the same destination, usually for a subdomain-based Multisite network. | *.example.com A 192.0.2.1 |
It expands the operational blast radius. An explicit record such as blog.example.com normally takes precedence for that name. |
For one blog, use an explicit A record or provider-supported CNAME. Do not add a wildcard merely because the blog is on a subdomain. A wildcard is useful when many hostnames must reach the same server and the web server is prepared to route them safely.
Add the record without disturbing the main site
- Find the authoritative DNS provider for
example.com. Edit the zone there, not at a secondary registrar interface that does not control the active nameservers. - Create
blogas the host label. Enter the destination IP for an A record or the provider’s hostname for a CNAME. Leave existing records for the apex domain,www, mail, and other services unchanged. - Use a normal TTL appropriate for your provider. During a planned migration, lower the TTL before the change if you control the timing; already-cached answers can remain visible until their previous TTL expires.
- Query more than one resolver after saving the record. For example, run
dig +short blog.example.comanddig @1.1.1.1 +short blog.example.com, then check a resolver on a different network. The answers should match the intended address or target hostname.
DNS propagation is not a signal that the web server is ready. A correct DNS answer can still produce a default hosting page, a certificate warning, a 404, or a redirect to the wrong site until the destination is configured.
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.
Configure the destination web server
Add the hostname before directing real traffic. The server must have the WordPress files, a database connection, a supported PHP version, PHP extensions required by your plugins, and write access to wp-content/uploads where uploads are expected.
Apache virtual host
Point a virtual host at the directory containing wp-admin, wp-content, and wp-includes. A minimal HTTP example is:
<VirtualHost *:80>
ServerName blog.example.com
DocumentRoot /var/www/blog
<Directory /var/www/blog>
AllowOverride All
Require all granted
</Directory>
</VirtualHost>Enable the site, make sure the rewrite module is available, and reload Apache. AllowOverride All is one common way to let WordPress use its .htaccess rules; a locked-down server can instead place equivalent rewrite directives directly in the virtual host. Confirm that the selected PHP handler is the one used by this virtual host rather than by another site on the machine.
Nginx server block
For Nginx, the critical pieces are the exact server_name, the WordPress document root, a fallback to index.php, and a PHP upstream:
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.
server {
listen 80;
server_name blog.example.com;
root /var/www/blog;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ .php$ {
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/run/php/php-fpm.sock;
}
}The PHP-FPM socket differs by operating system and installed PHP version, so use the socket or upstream defined by your server. Restrict execution in upload directories according to your platform’s security guidance. Reload Nginx only after its configuration test succeeds.
Prevent the wrong virtual host from answering
If the IP hosts several sites, an omitted or misspelled hostname can select the first/default site. Request the site by hostname, not by IP, and inspect the response headers and page title. A temporary diagnostic file in the intended document root can confirm routing, but remove it before launch.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Install TLS and establish the canonical HTTPS URL
Obtain a certificate whose names include blog.example.com. A wildcard certificate can cover multiple subdomains, but it is not required for one explicit hostname. Configure the certificate and private key on the destination server or on the trusted reverse proxy that terminates TLS.
- Serve the certificate on port 443 for
blog.example.com. - Keep port 80 available long enough to issue a permanent redirect to the HTTPS hostname.
- Test the certificate chain, hostname match, expiration, and renewal process from outside the server.
- In WordPress, open Settings > General and set both WordPress Address (URL) and Site Address (URL) to
https://blog.example.com. - Save once, then sign in again using the HTTPS address. Do not switch only one of the two URL fields.
If the site is being moved from another URL, take a file and database backup first. Hard-coded links, serialized option values, attachment metadata, and plugin settings may still contain the old address. A search-and-replace tool that understands serialized data is safer than a blind SQL replacement. With WP-CLI, a cautious pattern is:
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
wp search-replace 'https://old.example.com' 'https://blog.example.com' --all-tables --skip-columns=guid --dry-run
wp search-replace 'https://old.example.com' 'https://blog.example.com' --all-tables --skip-columns=guidReview the dry-run count and limit the tables or old URL if the database contains unrelated sites. Update the home and siteurl options only after confirming the replacement scope. Keep the old host available for a controlled redirect if it previously served the blog, but do not allow both hosts to generate independent canonical pages.
Handle a reverse proxy or CDN correctly
A proxy is optional. If one sits between visitors and WordPress, it must preserve the original host and scheme. WordPress needs to know that the public request was for blog.example.com over HTTPS, even if the proxy connects to the origin over HTTP.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Forward the original
Hostvalue, or provide a trustedX-Forwarded-Host. - Forward the original protocol in
X-Forwarded-Proto: https. - Configure the origin to trust these headers only from the proxy’s network; accepting arbitrary forwarded headers from the public internet enables host-header and redirect problems.
- Ensure the proxy’s TLS certificate covers the public subdomain and that its health check uses the same hostname.
If the proxy overwrites HTTP_HOST, WordPress can create links for the origin hostname or repeatedly redirect between HTTP and HTTPS. The WordPress reverse-proxy guidance documents using the forwarded host or a correctly set SERVER_NAME. A typical trusted-proxy adjustment in wp-config.php is:
if (!empty($_SERVER['HTTP_X_FORWARDED_HOST'])) {
$_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'];
}
if (!empty($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
$_SERVER['HTTPS'] = 'on';
}Use this pattern only when the proxy strips or sets the headers reliably. Otherwise, configure the proxy and origin so WordPress receives the correct values without application overrides. If you define WP_HOME and WP_SITEURL constants, use the final HTTPS subdomain and avoid conflicting database values.
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.
Set up WordPress for the new hostname
New installation
- Create the database and database user on the destination server.
- Place WordPress in the document root selected by the virtual host.
- Complete the installer while visiting
https://blog.example.com, not the server IP or a temporary hostname. - Save permalinks under Settings > Permalinks. This refreshes rewrite rules after the server configuration is ready.
- Install only the themes and plugins that the independent site needs, then configure backups before publishing.
Existing installation moved to the subdomain
Copy files and the database, update the URL in a controlled maintenance window, and preserve file ownership and permissions. Verify that uploads, cache directories, and generated configuration files belong to the account used by PHP. If the old installation remains live during DNS propagation, prevent it from accepting new content that will not be copied to the destination.
Check login cookies carefully. A cookie domain fixed to example.com can create collisions with another WordPress installation; do not set a parent-domain cookie unless sharing authentication is intentional and tested. Clear old browser cookies when diagnosing login loops.
Free tools Windows power users keep installed
One-click scans. No signup required.
Multisite-specific work
For a subdomain-based network, the wildcard record and matching server alias must exist before creating sites. In Network Admin, confirm the network’s domain and path settings, then add or map the blog hostname through the supported network workflow. Update every stored site address when a domain changes. Merely changing SUBDOMAIN_INSTALL or rewrite rules does not migrate existing addresses, configure DNS, create virtual hosts, issue certificates, or repair cookies.
Test the complete request path
Run these checks from an external connection and, where possible, from more than one browser:
- DNS: The subdomain resolves to the intended A record or CNAME, while the main domain still resolves to its original host.
- HTTP redirect:
curl -I http://blog.example.com/returns a redirect to the HTTPS subdomain, not to the main site or an origin hostname. - HTTPS: The certificate name matches, the chain validates, and the final URL remains HTTPS after several redirects.
- Front page and content: A post, category, tag, search result, pagination link, and a deliberately nonexistent URL behave as expected.
- Permalinks: Pretty URLs return WordPress content rather than server 404 pages. If they do not, resave permalinks and inspect the Apache or Nginx rewrite configuration.
- Media: Upload a new image, view it in a post, and inspect its URL for the correct HTTPS hostname. Check existing attachments after a migration.
- Administration: Log in, open the dashboard, edit a post, use the media library, and confirm that admin links do not switch hosts or protocols.
- REST and feeds: Request
/wp-json/, the RSS feed, and the generated sitemap. They should expose the public hostname consistently. - Cookies: Log out and back in, test a private browser window, and verify that cookies are scoped to the intended host.
- Background work: Confirm scheduled publishing, site health checks, email links, backups, and any external cron job use the new URL and can reach the destination.
- Canonical behavior: The preferred HTTPS URL appears in redirects, canonical tags, sitemap entries, and feeds; no duplicate HTTP or old-host version remains indexable.
Troubleshoot by symptom
| Symptom | Likely cause | Fix |
|---|---|---|
| DNS returns the old address | Record was added at the wrong DNS provider, a stale cache remains, or a conflicting record exists. | Check the authoritative nameservers, query them directly, remove the conflict, and wait for cached TTLs to expire. |
| Default hosting page appears | The destination lacks a matching ServerName or server_name, or the request reaches the wrong virtual host. |
Add the exact hostname, enable the site, reload the server, and test with the hostname rather than the IP. |
| Certificate warning | The certificate omits the subdomain, the proxy serves a different certificate, or the chain is incomplete. | Issue or select a certificate covering the exact public hostname and configure it at the TLS termination point. |
| Redirect loop | The proxy says the request is HTTP while the browser is HTTPS, or WordPress URL settings disagree with the proxy. | Preserve X-Forwarded-Proto, configure trusted handling, and make both WordPress URL fields use the HTTPS address. |
| Every post URL is a 404 | Rewrite rules are disabled, .htaccess is ignored, or Nginx lacks the try_files fallback. |
Enable the appropriate rewrite mechanism, resave permalinks, and inspect server error logs. |
| Login returns to the login page | Host or scheme changes invalidate cookies, or a parent-domain cookie collides with another site. | Fix forwarded host and HTTPS detection, remove an unnecessary COOKIE_DOMAIN, clear cookies, and retry. |
| Images still use the old host | Database values, serialized plugin settings, cached HTML, or CDN metadata retain the former URL. | Run a serialized-data-aware replacement, purge the relevant cache, and verify newly generated media URLs. |
| Admin links point to the origin server | The proxy overwrites the host or WordPress constants contain the origin URL. | Preserve the public host, correct trusted forwarded-header handling, and remove conflicting URL constants. |
Operate and roll back safely
- Take a database and file backup before changing URLs, DNS, or Multisite network settings. Test that the backup can actually be restored.
- Document the previous DNS record, TTL, server configuration, certificate location, and WordPress URL values. This makes rollback a deliberate change rather than guesswork.
- Keep the destination ready before switching DNS. If the blog is business-critical, make the old host serve a temporary redirect only after the new host has been verified.
- Automate certificate renewal and monitor renewal failures; an expired certificate makes a correctly routed site unusable.
- Keep WordPress core, plugins, themes, PHP, and the operating system patched. Separate hosting does not remove the need to maintain the blog server.
- Back up the independent site on its own schedule. In Multisite, confirm that backups include the network database, each site’s tables, uploads, and shared code.
- Do not enable strict transport policies or aggressive caching until HTTPS, redirects, login, REST requests, and administrative access work consistently.
A practical launch sequence
- Choose independent WordPress or Multisite based on governance and backup boundaries.
- Prepare the destination files, database, PHP handler, document root, and server block.
- Create the explicit A or CNAME record; use a wildcard only for a genuine multi-subdomain design.
- Verify DNS from multiple resolvers while the destination still serves a controlled test response.
- Install the certificate for
blog.example.comand configure HTTP-to-HTTPS redirection. - Set both WordPress URL fields to
https://blog.example.com; migrate stored URLs with a serialized-data-aware tool if necessary. - Configure forwarded host and scheme handling if a proxy is present.
- Resave permalinks, test login, media, REST, sitemap, cron, redirects, and canonical URLs.
- Monitor logs and uptime after launch, and keep the documented rollback record until DNS caches for the previous configuration have expired.
The result is a normal WordPress site whose public hostname happens to be a subdomain: the main domain can remain on its existing host, while the subdomain resolves and operates on the second server. The reliable boundary is clear—DNS selects the destination, the destination server routes the hostname, and WordPress must be configured to recognize and publish that hostname over HTTPS.
Quick Recap
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.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
