Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →To connect a .si domain to a website, add the exact DNS records your website host provides at the domain’s authoritative DNS provider—or change the domain’s nameservers if your provider requires it. The registrar, DNS host and website host can be three different companies. Before changing nameservers, copy any email and other service records so they are not lost.
Understand which provider controls each part
Your registrar manages the domain registration and its delegation. Your DNS host publishes the records that direct domain names to services; it may be the registrar or a separate provider. Your website host tells you which records or nameservers it needs. Make DNS changes wherever the domain’s current authoritative nameservers point, rather than assuming the registrar’s portal is the right place.
.si is Slovenia’s country-code top-level domain, managed by the Academic and Research Network of Slovenia (ARNES), according to IANA’s .si delegation record. That registry role does not mean ARNES hosts every .si domain’s DNS or website.
Choose whether to keep DNS hosting or change nameservers
| Approach | What changes | When it fits | Main risk |
|---|---|---|---|
| Keep current nameservers | Add the website host’s requested records to the existing DNS zone. | You only need to point website hostnames to a site, and the current DNS provider supports the required records. | Incorrect or conflicting records can prevent the website hostname from resolving as intended. |
| Change nameservers | Replace the domain’s current delegation with all nameservers supplied by the new DNS or website provider. | The destination provider explicitly requires or materially benefits from managing the whole DNS zone, and you have migrated its records. | Moving the zone without recreating records can interrupt email, verification, subdomains or other services. |
Keeping the existing nameservers and adding only the website records usually limits the change to the web hostnames. A nameserver change transfers control of the whole zone, not just the website.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
Connect the domain using your host’s exact values
- Identify the authoritative DNS provider. Check the domain’s nameserver settings or use a DNS lookup tool, then sign in to the provider responsible for those nameservers. If you are unsure, ask the registrar which nameservers are currently delegated.
- Open the website host’s custom-domain instructions. Add the domain in the host’s dashboard if required. Copy the exact record type, hostname or name, and target or value the host specifies. There is no universal IP address or CNAME target for all websites.
- Add the requested records in the DNS zone. Hosts commonly request an A or AAAA record for the apex domain (for example,
example.si), a CNAME forwww, or a provider-specific combination. Treat those as examples of record types, not values to enter without checking your host’s instructions. Follow the host’s directions if it specifies an apex alias or another provider-specific setup. - Save and check for conflicts. If an existing record uses the same hostname, determine whether the host instructs you to replace it. Avoid keeping conflicting records for the same name unless the provider explicitly requires them.
- Verify both web addresses. Use the host’s custom-domain status or verification tool, if available, and check both the apex domain and
www. They may need separate DNS records or a redirect configured in the hosting platform. - Enable HTTPS through the host. Once the host recognizes the domain, follow its process to issue or activate the site certificate. Correct DNS alone does not configure HTTPS.
If your provider requires a nameserver change
- Export or record the current DNS zone. Preserve every record still needed, particularly MX records for email, TXT records for email authentication or domain verification, and records for subdomains or other services.
- Recreate those records with the new DNS provider. Add the website host’s records too, using the exact values supplied by the relevant providers. Confirm the new zone is complete before changing delegation.
- Change the nameservers at the registrar. Enter every nameserver supplied by the new provider in the registrar’s domain settings. Do not add just one if the provider supplied several.
- Check the new delegation and services. Run the .si Registry’s DNS check, then verify the website, email and other services that rely on the domain. If something fails, compare the new zone with your saved records and correct omissions or typos at the new DNS host.
Check .si delegation separately from website DNS
The .si Registry DNS check links to Zonemaster and checks the domain’s nameservers as well as the parent-zone nameservers. Register.si says a delegation needs at least two nameserver records; authoritative nameservers must be reachable over UDP and TCP port 53, serve consistent authoritative data, and not offer open recursive service. ERROR or CRITICAL results mean the domain will not be delegated to DNS.
This test concerns whether the .si domain is properly delegated to authoritative DNS. It does not establish that your website’s A, AAAA or CNAME record points to the correct host, that the host has accepted the custom domain, or that HTTPS is active. Use the registry check for delegation issues and the website provider’s own status tool for its configuration.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Allow time for DNS changes to appear
Register.si says .si zone updates have been hourly since March 15, 2025, rather than every other hour before that date. This is the registry’s parent-zone publication cadence—not a guarantee that every resolver, browser or device will show a change within an hour. DNS time-to-live settings and resolver caches can continue to return older answers temporarily.
The registry describes a pre-delegation verification schedule of checks every 10 minutes for the first eight hours after a nameserver change, hourly from 8 to 24 hours, and then daily. Adding or deleting a nameserver resets that schedule. These are registry checks, not a countdown that predicts when your website will work everywhere.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesProvider-specific help
DNS interfaces and support processes vary. For example, ARNES documents DNS hosting for its members and domain redirection to static or dynamic websites hosted with ARNES; it directs users who need a domain server or record changes to [email protected]. This guidance applies to eligible ARNES organizations, not every .si domain holder. Telekom Slovenije’s registrar instructions likewise describe its own customers’ domain portal and DNS support process, rather than a universal .si procedure.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
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.
