Four nameservers named ns-<number>.awsdns-<number>, one under each of .com, .net, .org and .co.uk, mean the domain’s DNS is in an Amazon Route 53 hosted zone. They are assigned to the zone and cannot be changed; a deleted and recreated zone gets four new ones.
| Whose | Amazon Route 53 — Cloud provider |
| Nameservers | ns-<n>.awsdns-<n>.com, .net, .org, .co.uk |
| How they are given | Four per hosted zone; the same four for many zones with a reusable delegation set |
| DNSSEC | Yes — signing with a key in AWS KMS, then the DS at the registrar |
Does your domain use Amazon Route 53’s nameservers?
Enter a domain: we ask its registry which nameservers it hands out, ask each of them for the zone, and say whose they are — and whether any does not answer or disagrees.
The names
Four names, one under each of awsdns-<n>.com, .net, .org and .co.uk — AWS’s own example:
ns-2048.awsdns-64.com
ns-2049.awsdns-65.net
ns-2050.awsdns-66.org
ns-2051.awsdns-67.co.uk
Where to see and change them
In the Route 53 console: Hosted zones, the zone, then Hosted zone details — the four names under Name servers. Registering a domain with Route 53 creates the zone and sets its nameservers for you.
Nameservers under your own domain (ns1.example.com …) are built on a reusable delegation set, with glue records at the registrar.
Worth knowing
Use all four. The NS records of a Route 53 zone usually have a TTL of two days, so resolvers can keep using the old nameservers that long after a change.
Common mistakes
- Giving the registrar the nameservers of another hosted zone with the same name: each zone has its own four.
- Deleting the hosted zone the domain uses: it goes offline, and a new zone gets different nameservers.
- Moving the DNS away with DNSSEC signing on: remove the DS record first — signing cannot run at two providers at once.
- Editing the zone’s own NS and SOA records, which AWS says to leave alone except in rare cases.
Also: Adding DNS records at Amazon Route 53; Turning on DNSSEC at Amazon Route 53.
Sources
Checked on 27 September 2026 against these official sources:
- NS and SOA records that Amazon Route 53 creates for a public hosted zone — docs.aws.amazon.com
- Configuring white-label name servers — docs.aws.amazon.com
- Making Route 53 the DNS service for a domain that’s in use — docs.aws.amazon.com
- Adding or changing name servers and glue records for a domain — docs.aws.amazon.com
- My domain is unavailable on the internet — docs.aws.amazon.com