Every domain "lives" on someone's DNS servers โ those servers store all A, MX, TXT and other records and answer queries from around the world. The NS record (Name Server) is the foundational element: it tells the global DNS system which servers are authoritative for your domain. A misconfigured NS makes a site unreachable or unstable.
NS records exist on two levels: first at the registrar (in the TLD), and second inside the domain's own DNS zone. The two must match โ a mismatch results in lame delegation and resolvers receive inconsistent answers.
Registrar NS vs hosting NS
A freshly registered domain uses the registrar's default name servers. That works for many, but switching to your hosting provider's NS is usually more convenient because the hosting panel manages A, MX and other records automatically with no manual edits during moves.
You change NS inside the registrar account by removing the defaults and entering two to four hostnames provided by hosting, such as "ns1.sayt.uz" and "ns2.sayt.uz". Propagation takes 24 to 48 hours as the new NS list spreads through resolvers worldwide.
NS propagation
Changing NS is one of the heaviest DNS operations because it transfers the entire zone owner. Other records use TTLs of 300โ3600 seconds, but NS often run at 86400 seconds or more. Resolvers caching old NS will not switch instantly.
During propagation different users see different servers depending on which resolver they use. To avoid trouble, prepare the new zone with identical records before the switch so visitors notice no difference.
Glue records and your own NS
If you want to run NS like "ns1.sayt.uz" you need a glue record. The logic is simple: to find "ns1.sayt.uz" the resolver must query the "sayt.uz" zone, but to enter that zone it needs to find "ns1.sayt.uz" โ a circular dependency.
Glue breaks the loop by letting the registrar publish the NS IP directly at the TLD. Most users do not need to deal with glue โ they use ready hosting NS, and the host has already configured glue in its infrastructure.
Lame delegation and common mistakes
Lame delegation is the most common NS mistake. It happens when an NS entry at the registrar points to a server that is not actually authoritative. Resolvers hit timeouts and users perceive the site as down.
Another mistake is forgetting to sync zones between old and new NS. If you swap NS without copying records to the new zone, some users see an empty site during propagation. Prepare the new zone in advance to avoid this.
Sayt.uz practice
73 percent of Sayt.uz domains use our NS โ "ns1.sayt.uz" and "ns2.sayt.uz". Those customers manage records in one panel and skip extra configuration when changing hosting. The remaining 27 percent rely on external DNS, most often Cloudflare.
Switching NS is free and takes a couple of clicks in the dashboard. A domain costs 119 000 soum per year with DNS included. Complex turnkey DNS configuration with our specialists starts at 150 000 soum and includes propagation monitoring.