You changed your nameservers or DNS records to point to Ultra Web Hosting, but when you visit your domain you still see the old site, a "coming soon" page, or the Ultra Web Hosting default page. This is almost always DNS propagation. DNS changes take time to spread across the internet, and until they do, different visitors may see different versions of your site depending on which DNS server they're using.
Wait 24-48 Hours After DNS Changes
DNS propagation takes anywhere from a few minutes to 48 hours. There's no way to force it faster globally. During this time:
- Some visitors see the old site, some see the new one
- Your ISP's DNS cache may take longer than others
- You can check propagation status at whatsmydns.net
- Test the new site using your hosts file (see Section 4)
01. What Is DNS Propagation
When you change nameservers or DNS records, the change starts at your domain registrar. But there are thousands of DNS servers around the world that cache your old records. Each one has a different expiry time (TTL - Time to Live) for its cache. Until a DNS server's cache expires and it fetches the new records, it keeps serving the old ones.
This is why some people see your new site while others still see the old one. It's not broken. It's just slow by design - DNS was built for reliability, not speed.
Typical propagation times:
- A record changes - usually 1-4 hours if the old TTL was low (300-3600 seconds)
- Nameserver changes - typically 12-24 hours, can take up to 48 hours
- Your ISP - some ISPs cache aggressively and take the full 48 hours
02. Check Your Propagation Status
Use whatsmydns.net to check DNS propagation worldwide. Enter your domain and select the record type (A for website, MX for email). Green checkmarks show servers that have the new records. Red X marks show servers still serving old records.
You can also check from your own computer:
# Windows (Command Prompt)
nslookup yourdomain.com
# Mac/Linux (Terminal)
dig yourdomain.com +shortCompare the IP address returned with your Ultra server's IP (found in your client area under service details). If they match, propagation has completed for your network.
03. Why You See the Ultra Web Hosting Homepage
If your domain resolves to the correct Ultra server IP but shows a default "Ultra Web Hosting" page instead of your website, DNS has propagated but your site files aren't in the right place. Check these:
- Files not uploaded yet - log into cPanel > File Manager and check that your website files are in
public_html. If it's empty or only has a defaultindex.html, upload your site files - Default index.html exists - cPanel creates a default
index.htmlwhen your account is provisioned. If your site usesindex.php(WordPress, etc.), the defaultindex.htmltakes priority. Delete or rename it - Addon domain files in wrong directory - if this is an addon domain, files go in the addon domain's directory (e.g.,
public_html/yourdomain.com), not in the primarypublic_html. Check cPanel > Domains to see the document root for your domain - Migration not complete - if you requested a free migration, it may still be in progress. Check your support ticket for status
If you're migrating from another host, you can verify the site works on Ultra before DNS propagates by editing your local hosts file. See Section 4 below.
04. How to Speed Up Propagation
You can't speed up global propagation, but you can make it faster for yourself and test your site before everyone else sees it:
Flush Your Local DNS Cache
# Windows
ipconfig /flushdns
# Mac
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux
sudo systemd-resolve --flush-cachesTest via Hosts File (See Your Site Immediately)
Edit your local hosts file to point your domain directly to your Ultra server IP, bypassing DNS entirely:
# Add this line (replace with your actual server IP and domain):
123.45.67.89 yourdomain.com www.yourdomain.comFile locations:
- Windows -
C:\Windows\System32\drivers\etc\hosts(edit as Administrator) - Mac/Linux -
/etc/hosts(edit with sudo)
After adding this, your browser will go directly to the Ultra server regardless of DNS. Remove the line once propagation is complete.
Remember to remove the hosts file entry after DNS propagates. If you leave it and the server IP ever changes, your domain will stop loading on your computer while working fine for everyone else.
Use Google DNS
Google's public DNS (8.8.8.8 and 8.8.4.4) typically picks up changes faster than most ISP DNS servers. Switching to Google DNS can help you see changes sooner.
05. It's Been 48+ Hours and Still Not Working
If it's been more than 48 hours and your domain still doesn't point to Ultra, something is misconfigured. Check these in order:
- Verify nameservers at your registrar - log into wherever you registered the domain and confirm the nameservers are set to
ns1.ultranameservers.com,ns2.ultranameservers.com, andns3.ultranameservers.com. Typos here are the most common cause - Domain not expired - check that your domain registration hasn't expired. An expired domain stops resolving entirely
- Domain lock - some registrars require you to unlock the domain before nameserver changes take effect. Check for a "Domain Lock" or "Transfer Lock" setting
- A record override - if you're using a third-party DNS provider (like Cloudflare) and changed nameservers, the A record at the old DNS provider may still be active. Update the A record there, or ensure nameservers were actually changed (not just A records at the old provider)
- Contact support - open a ticket with your domain name and what you see when you visit it. We can check the server-side DNS configuration and verify your account is set up correctly
Domain Still Not Resolving?
If DNS has propagated but your site still isn't showing correctly, open a ticket with your domain name and what you're seeing.
Open a Support TicketFrequently Asked Questions
Why does my site still show the old version after changing DNS?
Almost always DNS propagation. When you change nameservers or records, the update takes time to spread across the internet, and until it does, your computer may still use a cached old answer and show the previous site or a default page.
How long does DNS propagation take?
Usually a few hours, and up to 24 to 48 hours in some cases, depending on the TTL of the old records and your ISP's caching. You can check propagation with an online DNS checker to see which locations have picked up the new records.
Why do I see the Ultra Web Hosting default page?
You see the default page when DNS now points to our server but no site files are in the document root yet, or propagation is partway done. Upload your site to the correct document root such as public_html, and the default page is replaced once propagation completes.
My DNS change still is not working after 48 hours, what now?
Confirm the nameservers or A record actually point to your account, clear your local DNS cache and browser cache, and test from another network or a DNS checker. If the records are correct everywhere but the site still fails, open a ticket so we can check the server side.
Quick Recap
If you only do 5 things from this guide, do these:
- Wait 24-48 hours - DNS propagation is normal and cannot be forced
- Check propagation at whatsmydns.net - see which DNS servers have updated
- Flush your local DNS cache -
ipconfig /flushdnson Windows - Test with hosts file - bypass DNS to verify your site works on Ultra before propagation completes
- 48+ hours? Check nameservers - typos in nameserver names are the #1 cause of stalled propagation
Last updated November 2026 · Browse all DNS articles
