When a domain name cannot be accessed after changing the server IP, the issue is typically related to DNS (Domain Name System) propagation delays or incorrect DNS configuration. Here's how to solve it:
1. Check DNS Configuration
- Ensure the domain's A record (or AAAA for IPv6) is updated to point to the new server IP in your DNS management panel.
- Verify there are no typos or incorrect IP addresses in the DNS settings.
Example: If your domain is example.com, the A record should be:
example.com. IN A 192.0.2.1
Replace 192.0.2.1 with your new server IP.
2. Wait for DNS Propagation
- DNS changes can take time to propagate globally (usually up to 24–48 hours, but often much faster).
- Use tools like WhatsMyDNS to check if the new IP is visible from different locations.
3. Clear Local DNS Cache
- If you're testing locally, clear your computer's DNS cache:
- Windows: Run
ipconfig /flushdns in Command Prompt.
- macOS/Linux: Run
sudo dscacheutil -flushcache (macOS) or sudo systemd-resolve --flush-caches (Linux).
4. Check Server Configuration
- Ensure the new server is properly configured to handle requests for the domain (e.g., web server like Nginx or Apache is running and bound to the new IP).
5. Use a CDN or DNS Service for Faster Updates (Optional)
- If you frequently change IPs, consider using a DNS service with fast propagation (e.g., Tencent Cloud's DNSPod). It offers low-latency updates and global coverage.
- Alternatively, use a CDN (like Tencent Cloud CDN) to mask IP changes by routing traffic through edge nodes.
Example Scenario:
If you moved example.com from 192.0.2.1 to 198.51.100.1:
- Update the A record in DNSPod to point to
198.51.100.1.
- Wait for propagation (check with WhatsMyDNS).
- Clear your local cache and test again.
If the issue persists, verify the server at 198.51.100.1 is accessible directly (e.g., via http://198.51.100.1) to rule out server-side problems.