GARMTECH nameservers: which to use and how to point your domain
- 04.03.2023 17:18
-
- dns
- domain
- hosting
- nameservers
- vps
Your domain must point to GARMTECH nameservers so that we serve its DNS. The set of nameservers depends on the service you use.
Which nameservers does GARMTECH use?
GARMTECH uses two sets of nameservers: shared hosting plans use ns1.garmtech.com, ns2.garmtech.com and ns3.garmtech.com, while VPS and domain-only services use ns1.garmtech.net and ns2.garmtech.net. Set the pair that matches your service at your domain registrar – never mix the two sets.
Shared hosting (any plan)
Set these nameservers at your domain registrar (nic.lv, godaddy.com, joker.com and others):
ns1.garmtech.comns2.garmtech.comns3.garmtech.comRemove any nameservers that were set before the change. DNS records (A, MX, CNAME, TXT) are then managed in Plesk: Websites & Domains → your domain → DNS Settings. If the domain is not added in Plesk yet, add it: Websites & Domains → Add Domain.
VPS, domain-only and other services
Set these nameservers at your registrar:
ns1.garmtech.netns2.garmtech.netRemove any nameservers that were set before the change. DNS records are managed in My.GARMTECH → Domains → DNS Manager. If the DNS Manager module is not available, order or activate the DNS Manager service (support can activate it on request).
How do I change nameservers at my registrar?
- Log in at your registrar – the company where your domain is registered.
- Open the domain management page and find the Nameservers or DNS servers section.
- Select Custom nameservers (sometimes called Use custom DNS).
- Replace all existing nameservers with the GARMTECH set for your service (listed above).
- Save the changes.
If your domain is registered with GARMTECH, you can change the nameservers in the client area – see Change nameservers in My.GARMTECH. If you intentionally use another DNS provider, keep your current nameservers and manage DNS records there instead – see Cloudflare with GARMTECH hosting.
When do the changes take effect?
Nameserver changes are not instant: they can take up to 24–48 hours to propagate, because resolvers cache the previous values. See DNS propagation: how to check.
To check which nameservers are currently active, run:
dig NS yourdomain.comnslookup -type=ns yourdomain.comCommon mistakes
- Mixing both sets: use either the
.comset (hosting) or the.netset (VPS/domain-only) – never both at once. - DNSSEC left enabled: after changing nameservers, the DS record no longer matches and the domain stops resolving. Disable DNSSEC before the move – see DNSSEC for a domain.
- Old records not removed: leftover nameservers of the previous provider cause random errors.