When something breaks
How to connect a custom domain to your site
In short
To connect a custom domain to your site you need two things: add the domain to your project, and add a DNS record at your registrar — the pointer that tells browsers where to look for the site. In Netrun that is the "Domains" tab on the project page: enter the domain you bought, copy the record shown into your registrar panel, and press "Check". The platform verifies every domain you added in one pass and issues an HTTPS certificate for each of them, so there is nothing to buy or renew. Custom domains are part of the Pro plan, and you can connect as many as you need to one site.
Connecting a custom domain feels confusing for one reason: the domain and the site live in different places. You bought the domain at a registrar, the site runs on a host, and nothing links them until you create that link yourself. The link is a DNS record: a short pointer that tells browsers which server to look for the site on. Usually there is a second chore on top of it: SSL. You get a certificate, put it on the server, and remember to renew it in three months.
In Netrun only the DNS record is left. You open the "Domains" tab on your project, type in the address you bought, and the panel shows the exact record to add — type, name and value, ready to copy into your registrar. Then you press "Check": the platform confirms the domain points to the right place and issues HTTPS for it. You can attach as many domains to one site as you need, and each gets its own certificate.
Make sure this project actually needs a domain#
A custom domain makes sense for a website — something people open in a browser. A Telegram bot or a background script does not need one: nobody opens them at an address, they reach out to other services themselves. The exception is a bot with a web part, such as an admin page or an endpoint that receives updates: that is a website, and a domain fits it.
Buy the domain at a registrar#
The domain is bought separately, at any domain registrar — Netrun does not sell domains and is not a reseller. Pick the address you want people to see; the ending does not matter. After the purchase you get a control panel for the domain, and that is where you will add the record, so keep access to it.
Add the domain on the "Domains" tab#
Open the project in your dashboard, go to the "Domains" tab and type in the address you bought, exactly as you bought it. Every next domain is added the same way, and there is no limit of one address per site. Custom domains run on the Pro plan; on the free plan the tab shows the upgrade instead.
Add the DNS record at your registrar#
Once the domain is added, the panel shows a single DNS record with its type, name and value. Copy those three fields into the DNS settings at your registrar and save. If you also want the site to open with the www prefix, add one more record named www — the panel shows that one the same way. Registrar panels look different from one another, but the set of fields is always the same.
Press "Check" and give the record time to spread#
The "Check" button verifies every domain you added at once, so you do not have to press it separately for each address. A new DNS record does not spread across the internet instantly: usually minutes, sometimes a few hours — that is how DNS works and it is out of your hands. If the first check does not pass, wait a bit and press it again. Once a domain is confirmed, the platform issues an HTTPS certificate for it and renews it on its own.
Work through the usual reasons a domain is not picked up#
There are three common ones. First, the record was added in the wrong place — for example in an old hosting panel while the domain is managed at the registrar, or the other way round. Second, the domain sits behind a third-party proxy mode, so traffic goes through that service and the check sees an address that is not yours; turn the proxy off. Third, the domain was just bought and is not delegated yet, so its DNS settings do not apply. All three sit on the domain side rather than the hosting side, so moving to another host does not fix them. While you sort it out, the site stays reachable at its Netrun link.
The result is a site that opens at your own address with the padlock in the browser, while the Netrun link stays as a working backup — it cannot be removed, and the site is reachable through it even if something is off with the custom domain. You never renew the certificate by hand: the platform does that as long as the domain is attached. Custom domains come with the Pro plan, and the current terms are visible in your dashboard. Try Netrun.
Common questions
How long until the domain starts opening the site?
Usually a few minutes to an hour, sometimes several hours. That is how DNS behaves: providers and browsers remember the previous answer for a while and do not refresh it right away. No host can speed that up, so wait and press "Check" again.
Why does the site open without www but not with www?
To a browser the address with the www prefix and without it are two different names, and each needs its own pointer. Add a second record named www at your registrar, then press the same "Check" button. After that the site opens both ways, and both get HTTPS.
What should I do if domain verification keeps failing?
First check that the record sits where the domain is actually managed — a common mistake is adding it in an old hosting panel while the domain points at the registrar. Then check whether the domain is behind a third-party proxy mode, which replaces the address so the check does not see your site. And if the domain was bought moments ago, give it time: until it is delegated, DNS settings do not take effect.
Does the original Netrun link keep working?
Yes, it always works and stays as a backup address for the site. It cannot be deleted, which is handy: if anything goes wrong with the custom domain, the site is still reachable. You can share either address.
Can I move a domain from an old host without downtime?
Yes. Publish the site on Netrun first and confirm it opens at the service link, and only then change the DNS record at your registrar. While the record spreads, some visitors still land on the old site and some on the new one, so do not shut the old one down immediately.
Does a Telegram bot need a custom domain?
No. A bot is opened in the messenger, not at an address in a browser, so a domain gives it nothing. A domain is only useful when the project has a web part — a site, an admin page, or an endpoint that receives requests over a link.
Can I connect my own domain?
Yes, on the Pro plan, and not just one: you can connect as many of your own domains to a website as you need. Open the “Domains” tab on the project page, enter the domain you bought from a registrar, and add the DNS record shown in the hint — every next domain is added the same way. Once the domains are ready, press “Check”: Netrun checks them all at once and issues a separate HTTPS certificate for each, so a hiccup with one domain does not hold up the others. The site opens at any of your addresses, and the Netrun link stays as a backup. If you connect a whole domain (for example myshop.com), you can add one more record so the site also opens with www. This is for websites — a bot or a background script does not need a domain.
Do I need to buy a domain and set up HTTPS?
No. Netrun gives your project a public address with HTTPS right away — the link with the padlock works out of the box. There is no domain to buy and no certificates to fuss with, it is all already included.
What is different about the Pro plan?
On the Pro plan your project runs around the clock: a website does not sleep and responds instantly, with no pause to wake up, while a bot or a background script keeps running with no 3-day limit. On top of that, Pro gives more memory, CPU and disk space, and a Pro website can use your own domains — as many as you need, each with HTTPS.