Host Preview Tool
DNS Testing & Server Migration
Test DNS configuration and preview websites on new servers before DNS propagation completes. Perfect for zero-downtime server migrations.
On This Page
What is Host Preview?
Host Preview is a powerful tool that allows you to test how your website will look and function on a new server before you change your DNS records. This is essential for server migrations, hosting provider changes, and infrastructure updates.
When you migrate a website to a new server, DNS propagation can take 24-48 hours to complete globally. During this time, some visitors see the old server while others see the new one. Host Preview lets you verify everything works perfectly on the new server before making the switch.
How It Works
Technical Overview
Host Preview works by creating a temporary subdomain that points directly to your new server's IP address, bypassing normal DNS resolution. Here's the process:
- 1.You provide your domain name and new server IP address
- 2.We create a temporary subdomain (e.g., abc123-yourdomain.hostpeeker.com)
- 3.This subdomain points directly to your new server's IP
- 4.You can access your site through this URL to test everything
- 5.The preview URL expires after 60 minutes for security
Common Use Cases
Server Migration
Test your website on a new hosting provider before switching DNS. Verify databases, file permissions, and configurations work correctly.
Infrastructure Updates
Preview your site after server upgrades (PHP version, web server changes, etc.) before applying changes to production.
Load Balancer Testing
Test specific servers behind a load balancer to diagnose issues or verify new server deployment.
CDN Bypass
Access your origin server directly, bypassing CDN caching to test changes or debug issues.
Step-by-Step Guide
Prepare Your New Server
Before using Host Preview, ensure your new server is completely set up:
- Web server (Apache/Nginx) installed and configured
- Website files uploaded to the correct directory
- Database imported and configured
- Virtual host configured for your domain
Get Your Server IP
Find your new server's public IP address. You can get this from:
- • Your hosting provider's control panel
- • Server command line:
curl ifconfig.me - • DNS lookup if you already have a DNS record pointing to it
Use the Host Preview Tool
Navigate to the Host Preview tool and enter:
- • Domain: Your website domain (e.g., example.com)
- • Server IP: Your new server's IP address
Test Your Website
You'll receive a temporary URL. Use it to thoroughly test:
- ✓ Homepage loads correctly
- ✓ All pages are accessible
- ✓ Images and media display properly
- ✓ Forms work and submit data
- ✓ Database queries execute correctly
- ✓ SSL certificate is valid (if using HTTPS)
- ✓ Redirects work as expected
Update DNS Records
Once you've verified everything works, update your DNS:
- 1. Log in to your domain registrar or DNS provider
- 2. Update the A record to point to the new server IP
- 3. Lower TTL before making changes (optional, for faster propagation)
- 4. Wait for DNS propagation (typically 1-24 hours)
Best Practices
Test During Off-Peak Hours
Test your new server during low-traffic periods to avoid any potential issues affecting users.
Check Browser Console
Open your browser's developer tools (F12) and check the console for JavaScript errors or broken resources.
Test Multiple Pages
Don't just test the homepage. Navigate through different sections, test forms, user logins, and e-commerce checkout if applicable.
Mobile Testing
Test the preview URL on mobile devices to ensure responsive design works correctly on the new server.
Troubleshooting Common Issues
Preview URL Shows "Connection Refused"
Cause: The web server isn't running or firewall is blocking connections.
Solution: Check that Apache/Nginx is running and firewall allows HTTP/HTTPS traffic (ports 80/443).
Site Displays Default Server Page
Cause: Virtual host not configured correctly for your domain.
Solution: Configure your web server's virtual host to respond to the preview subdomain or any hostname.
Images or CSS Not Loading
Cause: Hardcoded absolute URLs or incorrect base path in your application.
Solution: Use relative URLs or configure your application to accept requests from any hostname.
Database Connection Errors
Cause: Database credentials not updated or database not imported.
Solution: Verify database credentials in your config files and ensure the database is properly imported.