To point a .si domain at a website, either add the exact DNS records your website host provides in the domain’s active DNS zone, or change the domain’s nameservers to the set supplied by your new DNS provider. The right choice depends on who will manage DNS and whether you need to preserve email or other services. There is no universal A-record IP address or CNAME target for .si domains.
Choose between editing records and changing nameservers
| Approach | What changes | When it fits | What to watch |
|---|---|---|---|
| Edit DNS records | Keep the existing DNS provider and add or update the website records there. | You want to retain control of the current DNS zone, including email records, or your host supports connection by DNS records. | Use the exact values supplied by the website host. Avoid conflicting or duplicate records. |
| Change nameservers | Move authority for the whole DNS zone to the new nameservers. | Your website host or chosen DNS provider requires or you prefer delegation. | Recreate the website, email, and other service records at the new provider before or during the move. |
Google documents record-based domain connection and warns that nameserver changes may require restoring Google Workspace records; see Google’s DNS record guidance. Shopify recommends its default nameservers unless DNS is hosted elsewhere and warns that custom nameserver mistakes can affect connection and email; see Shopify’s domain connection instructions. WordPress.com describes connecting with records as an option when you need to keep email or cannot change nameservers: WordPress.com’s existing-domain guide.
As an Amazon Associate I earn from qualifying purchases.
Find the active DNS zone and your host’s exact values
- Identify the domain registrar and the provider currently hosting authoritative DNS. They may be different companies; changing settings at the registrar does not necessarily edit records in the active DNS zone.
- Open your website host’s domain-connection instructions for this domain. Copy the exact A, AAAA, CNAME, or nameserver values the host specifies. Do not use example values from another provider.
- Decide whether to edit records at the current DNS host or move the whole zone by changing nameservers. If the domain handles email or other services, note the records those services require before making changes.
An A record points a hostname to an IPv4 address; a CNAME points a hostname to another domain name. The website provider supplies the destination values. A common hostname for a CNAME is www, but the correct record depends on the host’s instructions. Google’s record guidance and Shopify’s manual connection guide explain their respective requirements.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchAdd records while keeping your current DNS provider
- Sign in to the account for the provider that hosts the active DNS zone and open the DNS management page for your .si domain.
- Add or update the website host’s requested records, matching each hostname, record type, and destination exactly. For example, the apex hostname is the bare domain such as
example.si, whilewww.example.siis a separate hostname. - Check for existing records that conflict with the new instructions. Do not remove email or other service records unless you know they are no longer needed.
- Save the zone changes, then allow the update window stated by the host. Google says changes may take up to 72 hours; Shopify gives up to 24 hours in its DNS editing guidance. These are provider-specific estimates, not a .si registry guarantee.
- Test the bare domain and the
wwwhostname if you intend to use both. Confirm that each reaches the expected site, and configure any desired redirect between them in the website platform.
Change nameservers without losing other services
- At the new DNS provider, create or prepare the zone for the .si domain. Add the website records and any records needed for email or other services.
- At the registrar, replace the current nameserver delegation with the complete set supplied by the new DNS provider. Register.si requires at least two nameservers for a .si delegation.
- Run Register.si’s Zonemaster DNS check for the proposed delegation. The registry checks that listed servers respond over UDP and TCP on port 53, answer authoritatively, provide consistent information, and match the parent delegation. ERROR or CRITICAL findings prevent delegation.
- After correcting any findings, submit the nameserver change through the registrar and monitor the domain, website, email, and other services.
Register.si says its checks run every 10 minutes during the first eight hours after a nameserver change, hourly from 8 to 24 hours, and daily thereafter; adding or deleting a nameserver resets this checking schedule. A technical contact receives a success notice or error report. These are registry delegation checks, not a promise that every visitor’s DNS cache updates on the same schedule. See the Register.si technical check page.
#1 Best Overall
Keep email and DNSSEC in mind
Email and other records
A nameserver change moves authority for the entire DNS zone, not just the website. If the new zone lacks the records your email or other services depend on, those services can stop working. Prepare the new zone before switching and confirm the records against the relevant service provider’s instructions. Google explains that Workspace records may need to be restored after a nameserver change in its DNS guidance.
DNSSEC
DNSSEC is not required simply to point 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, clocks are incorrect, or firewalls block larger DNS replies. If you change DNS providers while DNSSEC is enabled, coordinate the signing keys and parent DS records with both providers. Register.si’s DNSSEC Practice Statement, version 1.2, was updated and published on March 8, 2025; it describes verification of submitted DS records against matching DNSKEY records, with a documented registrar bypass. Read the Register.si DNSSEC information and DNSSEC Practice Statement.
Quick Recap
Rank #4
Rank #3
- Used Book in Good Condition
Troubleshoot a domain that does not reach the site
- Check active nameservers first. If the domain is delegated to a different DNS provider than the one whose records you edited, those edits will not control the live zone.
- Compare the records with the host’s instructions. Verify the hostname and record type as well as the target. A target copied from another platform may be wrong.
- Look for conflicting records. Multiple or incompatible records for the same hostname can prevent the intended connection.
- Check both hostnames. The apex domain and
wwware distinct; make sure the host’s setup covers each one you plan to use. - For a nameserver move, check the delegation. Run Register.si’s Zonemaster check and resolve any ERROR or CRITICAL findings.
- If email stopped working, inspect the new zone. Confirm that its email-related records match the instructions from your email provider.
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.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
