DNS access errors block Re-Leased — restore access now
If you see “site not found” or similar connection errors when opening Re-Leased, stale DNS data on your device or network is likely the cause. Start with a short wait, then clear the DNS cache in your browser or Windows, or involve your IT team if your network manages DNS.
Wait for automatic DNS refresh
Most DNS issues resolve on their own within minutes to a few hours as your device or network refreshes DNS data.
If you are not in a rush, wait and try again. This is the simplest and safest option.
Clear Chrome DNS cache
- Open Google Chrome.
- In the address bar, type
chrome://net-internals/#dnsand press Enter. - Click the Clear host cache button.
- Try opening Re-Leased again. You don’t need to restart Chrome.
Flush Windows DNS cache
- Click Start, type
cmd, and press Enter to open Command Prompt. - In the Command Prompt window, type
ipconfig /flushdns. - Press Enter.
You should see a message confirming the DNS cache was cleared.
Escalate to your IT team
If your organisation uses an internal DNS server, proxy, or firewall, your IT team may need to clear the DNS cache on their side. Let them know you are having trouble accessing Re-Leased and suspect stale DNS records.
Expect automatic resolution for most users
Most users will never run into this issue. If you do, the steps above usually restore access quickly.
Troubleshooting doesn’t restore access — contact Support
If you still can’t access Re-Leased after trying the steps above, contact our support team so we can help you quickly.
Share key details to speed up help
Please contact our support team and include:
- What you’ve tried so far
- When the issue started
- A screenshot of the error (if possible)
We’ll be happy to help further.