To connect a .si domain to a website, add the exact DNS records your website host provides to the domain’s authoritative DNS host—or change the domain’s nameservers if the new provider is meant to manage the entire DNS zone. The registrar, DNS host and website host may be three different services. Before changing nameservers, copy any email and other service records you need to keep.
Understand which provider controls each part
Your registrar manages the domain registration and its delegation. Your DNS host publishes records such as A, CNAME, MX and TXT. Your website host tells you which records or nameservers will direct visitors to its service. One company may provide all three, but that is not guaranteed.
Find the domain’s current nameservers and identify the provider operating them. Make website DNS changes in that provider’s DNS zone. If DNS is hosted elsewhere, changing records in the registrar’s portal may have no effect; use the registrar’s portal only for settings it controls, such as nameserver delegation.
Choose whether to keep DNS or move it
| Approach | What changes | When it fits | Main consideration |
|---|---|---|---|
| Keep the current nameservers | Add the website host’s required records to the existing DNS zone. | You want to connect the website while keeping the current DNS provider and other services. | Use the exact record type, name and value supplied by your website host. The provider may require an apex A or AAAA record, a www CNAME, or another combination. |
| Change nameservers | Change the domain’s delegation to the nameservers supplied by the new DNS provider. | You want that provider to manage the whole DNS zone, or it explicitly requires the change. | Recreate required email, verification and subdomain records at the new DNS host before switching. |
Keeping current nameservers and adding only the website records usually limits the change to the website hostnames. A nameserver change transfers control of the entire zone, not just the website.
#1 Best Overall
- Used Book in Good Condition
Connect the domain using the host’s instructions
- Get the connection values from your website host. Open its custom-domain or domain-connection instructions and note each required record’s type, host/name and value or target. Do not use example IP addresses or targets from generic guides: there is no universal DNS value for every website.
- Open the authoritative DNS provider’s zone editor. Add the records exactly as specified, observing the provider’s format for the root or apex name and for
www. If the host requires a nameserver change instead, use the registrar’s domain or nameserver settings and enter every nameserver it supplied. - Preserve other DNS services. Before a nameserver switch, make sure the new DNS zone contains the existing records needed for email and any other services, including MX and TXT records, verification records and subdomains. If you are only adding website records to the current zone, avoid altering unrelated records.
- Save and verify at the website host. Use its custom-domain status or check tool, if available. Check both the apex domain (the name without
www) andwww; they may need separate records or a redirect configured by the host. - Enable HTTPS through the website host. Follow its process after it recognizes the domain. DNS pointing alone does not establish that HTTPS is configured.
Check .si nameserver delegation
Register.si’s DNS check links to Zonemaster and tests delegation by querying both the domain’s nameservers and the parent-zone nameservers. Register.si says a delegation needs at least two NS records; the authoritative nameservers must answer over both UDP and TCP on port 53, serve consistent authoritative data, and not provide open recursive service. ERROR or CRITICAL results mean the domain will not be delegated to DNS.
This check concerns whether the .si delegation and nameservers meet registry requirements. It is not a test that your website’s A or CNAME record points to the correct destination, or that the website host has issued HTTPS.
Register.si’s published pre-delegation checking regime checks every 10 minutes during the first eight hours after a nameserver change, hourly from 8 to 24 hours, then daily. Adding or deleting a nameserver resets that regime. These are registry verification intervals, not a guarantee of when every user will see a website change.
Allow for DNS caching
Register.si has updated the .si zone hourly since March 15, 2025; previously, updates were every other hour. That cadence applies to publication of the .si parent zone. It does not force recursive resolvers, devices or browsers to discard cached DNS answers immediately. A previous destination may remain visible temporarily according to DNS TTLs and resolver caching.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteRank #3
Provider-specific .si notes
ARNES
ARNES documents DNS hosting for its members and domain redirection to static or dynamic websites hosted with ARNES. Its instructions direct users who need a domain server or record changes to contact hostmaster@arnes.si. These are ARNES-specific services and directions, not universal steps for every .si domain holder.
Telekom Slovenije
Telekom Slovenije’s registrar instructions illustrate that portal controls vary by provider: its customers edit DNS server settings in its domain portal and are told to notify its DNS support address. Follow the instructions for the company that actually manages your domain or authoritative DNS rather than assuming every .si registrar uses the same interface.
Quick Recap
Troubleshoot the common failure points
- The site does not change after editing records: confirm that you edited the zone at the authoritative DNS host, and compare the saved record with the website host’s exact instructions. Check for cached answers before making repeated changes.
- Email stops working after a nameserver switch: the new DNS zone may be missing the old mail-related records. Restore the required MX and TXT records, along with other records the mail provider specifies, in the active zone.
- The .si check reports ERROR or CRITICAL: use the checker’s findings to investigate delegation, nameserver reachability, consistency, or the two-NS minimum. A website record change cannot fix an invalid nameserver delegation.
- The apex works but www does not, or vice versa: check whether the host requires separate records for the apex and
www, and whether it expects a redirect between them. - The domain resolves but HTTPS is not ready: complete the website host’s domain verification and HTTPS setup; valid DNS delegation and a correct web record do not by themselves configure a certificate.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
