Recommended Free Tools
To point a .si domain at a website, either add the exact DNS records supplied by your website host at the service currently managing your DNS, or change the domain’s nameservers to the set supplied by the new DNS provider. The right choice depends on where you want to manage DNS and whether the domain already supports email or other services. Do not guess record values: they are specific to your host.
Choose between editing DNS records and changing nameservers
Your registrar and DNS host may be different companies. The registrar controls the domain’s delegation; the authoritative DNS host serves the records that direct web, email, and other traffic.
| Approach | What changes | When it fits |
|---|---|---|
| Add or update records | Keep the current DNS provider and change the records in its DNS zone. | Use this when you want to retain DNS management where it is, or need to preserve existing email and service records. Your website host must provide the required record values. Google’s and Shopify’s instructions explain host-specific A and CNAME records: Google and Shopify. |
| Change nameservers | Move authority for the entire DNS zone to the provider whose nameservers you enter at the registrar. | Use this when the website or DNS provider requires delegation, or you want that provider to manage the zone. Create the website, email, and other needed records at the new DNS host before or during the switch. Shopify recommends its default nameservers unless DNS is hosted elsewhere; WordPress.com describes record-based connection as useful when retaining email or when nameservers cannot be changed. |
Neither approach is automatically right for every .si domain. Base the choice on who will maintain the DNS zone, whether its existing records must remain available, and what the website provider requires.
Find the correct DNS values
Open your website provider’s domain-connection instructions for the specific domain, then copy the values it supplies. Depending on the provider and setup, you may be asked for an A record, AAAA record, CNAME record, or nameservers. An A record points a hostname to an IPv4 address; a CNAME points a hostname to another name. A common hostname for a CNAME is www, but the correct target is provider-specific. See the record guidance from Google and Shopify.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Do not copy sample values from another host or assume that all .si domains use the same destination. The registry does not provide a universal website IP address or CNAME target.
Point the domain step by step
- Identify the registrar and active DNS host. Check where the domain is registered and which nameservers it currently uses. The DNS zone may be managed outside the registrar account.
- Get the host’s exact connection values. In your website host’s domain setup, copy the records or complete nameserver set specified for your domain.
- Choose the change that matches your setup. For record-based pointing, edit the active DNS zone. For a nameserver move, change the delegation at the registrar and make sure the new DNS zone is ready.
- Protect email and other services. Before changing nameservers, copy or recreate the records those services need in the new zone. Google warns that Google Workspace records may need to be restored after a nameserver change; Shopify cautions that custom nameserver errors can affect both website connection and email. See Google’s record guidance and Shopify’s DNS guidance.
- Save the changes and allow time for updates. Follow your provider’s stated window rather than treating one estimate as universal. Google says updates can take up to 72 hours, while Shopify gives up to 24 hours for DNS editing; these are provider-specific estimates, not a .si registry guarantee. See Google and Shopify.
- Check both domain names you intend to use. Test the apex domain, such as
example.si, andwww.example.siif you want both to work. If the site does not load, confirm which nameservers are active, compare the record values with your host’s instructions, and look for conflicting records.
Meet .si nameserver delegation checks
If you change nameservers, Register.si requires at least two nameserver records in a .si delegation. Its Zonemaster-based DNS check tests whether the listed servers respond over UDP and TCP on port 53, answer authoritatively for the zone, provide consistent information, and match the proposed parent delegation. Register.si says ERROR or CRITICAL findings prevent delegation.
Register.si describes its verification schedule as 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 schedule. A technical contact receives a success notice or error report. These are registry delegation checks; they do not mean every visitor’s DNS cache updates on the same timetable. Details are on the Register.si DNS check page.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Account for DNSSEC if the domain is signed
DNSSEC is not required just to point a domain at a website. Register.si says an unsigned .si domain does not encounter DNSSEC validation problems. A signed domain can fail to resolve if signatures expire, DNSSEC is disabled without updating the parent zone, system clocks are wrong, or firewalls block larger DNS replies. See Register.si’s DNSSEC guidance.
Rank #3
- Used Book in Good Condition
If you move DNS providers while DNSSEC is enabled, coordinate the change with both providers so the parent DS data and the signing keys in the new zone remain aligned. Register.si’s DNSSEC Practice Statement, version 1.2, was updated and published on March 8, 2025. It says submitted DS records are checked against matching DNSKEY records before being added to the .si zone, except when a registrar uses the documented bypass command. See the Register.si DNSSEC page.
Quick Recap
Rank #4
Troubleshoot a domain that does not connect
- The website is not resolving after a nameserver change: Check the active delegation at the registrar, confirm at least two nameservers are listed, then run the Register.si DNS check and address any ERROR or CRITICAL findings.
- The domain resolves to the wrong place: Compare the active DNS records with the exact values in the website host’s instructions. Check for obsolete or conflicting records rather than adding more values by guesswork.
- The apex works but
wwwdoes not, or vice versa: Verify that the hostnames your site should serve each have the record type and destination required by the provider. - Email stops after a nameserver move: Review the new DNS zone for the email service’s required records and restore the values provided by that email service. A nameserver change moves the whole zone’s authority, not only the website entry.
- A signed domain fails to resolve: Check that the DNSSEC configuration at the registrar and authoritative DNS host is coordinated. Register.si lists expired signatures, mismatched changes, clock errors, and blocked large DNS responses among possible DNSSEC issues: DNSSEC guidance.
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.
