A name server (NS) defines which server's DNS records your domain points to. You'll need to change NS when moving your hosting from another company to Kolan IT, when connecting your domain to a third-party DNS manager like Cloudflare, or when switching to your own server. If your domain was registered with Kolan, this is done in a few steps from the client area.
1. Changing Name Servers from the Client Area
- Go to musteri.kolan.net.tr and sign in to your account.
- From the top menu, go to Domains → My Domains.
- Click the Manage button next to the domain you want to edit.
- Open the Name Servers option from the left menu.
- Check the Use custom nameservers option.
- Enter the NS addresses you want to use in Nameserver 1 and Nameserver 2 (the 3rd and 4th fields are required by some providers; leave them empty for most setups).
- Click the Change Nameservers button.
2. Switching Back to Kolan's Default Name Servers
If your hosting was purchased through Kolan, the default name server details were sent to you in your setup email at service activation. NS addresses are typically in the format:
ns1.kolan.net.tr
ns2.kolan.net.tr
You can switch back to Kolan's defaults in one click by checking the Use default nameservers option in the client area. If you don't know the correct values, you can open a support ticket and request the NS information specific to your account.
3. Switching to a Third-Party DNS Provider (Cloudflare, etc.)
If you want to connect your domain to Cloudflare, Google Cloud DNS, AWS Route 53 or another provider's DNS servers, the steps are:
- First, add your domain at the relevant provider and enter all your existing DNS records (A, AAAA, MX, TXT, CNAME) there one by one.
- The provider gives you two NS addresses (e.g. on Cloudflare
amir.ns.cloudflare.com,karen.ns.cloudflare.com). - Enter these NS addresses from the client area (follow the steps above).
4. DNS Propagation
A name server change doesn't become active worldwide instantly. The caches of ISPs and intermediate DNS servers need to refresh; this is called propagation and typically completes in 4 to 48 hours.
- In the first few hours, some visitors will see the old server and others the new one — this is normal.
- You can check the status from different locations with tools like whatsmydns.net.
- If you still see the old site in your own browser, clear your DNS cache (on Windows
ipconfig /flushdns, on macOSsudo dscacheutil -flushcache).
5. Common Errors and Solutions
- "Invalid nameserver" error: There's a typo in the NS address you entered, or that NS isn't registered yet. Copy the address from the provider and try again.
- Change hasn't reflected in 24 hours: If you still see the old site, it's most likely a local DNS cache. Test from a different device/network.
- Site opens but emails don't arrive: MX records are missing at the new name server. Add MX records from the DNS management panel.
- NS won't change on .tr domain: In some cases, NS changes for
.trextensions require nic.tr (TRABIS) approval; you may have to wait an additional hour.
If you've been having an issue for a long time after the NS change, or aren't sure which NS values to use, you can open a support ticket mentioning your domain; our team will inspect the current state and share the appropriate steps.