Theme

Popular tools

DreamHost Nameservers

DreamHost's nameservers are ns1–3.dreamhost.com. Copy them, then check your domain's zone at DreamHost before you switch.

DreamHost's own help pages · its nameservers asked directly · no log kept

DreamHost's nameservers

One shared setCloudflare · AS13335
  1. ns1.dreamhost.com162.159.26.14
  2. ns2.dreamhost.com162.159.26.81
  3. ns3.dreamhost.com162.159.27.84

Every DreamHost-managed domain uses these three names; a registrar normally needs only the names, not the addresses. DreamHost's guide

ns1–3.dreamhost.com

AsksDreamHostns1–3.dreamhost.comGlobalping

No domain at hand? Try , a site at DreamHost.

How to point a domain to DreamHost's nameservers

Add the domain to your DreamHost account first, then change the nameservers at the domain's registrar to ns1–3.dreamhost.com. Nothing is copied in the switch.

Your visitors keep reaching the old host until resolvers follow the new delegation.

Leaving DreamHost? Add every record at the new host first, then change the nameservers, and keep DreamHost's zone answering for the .com referral's 2 days.

The switch, in three placesDreamHost's help pages · October 24, 2026

  1. 1At DreamHost

    Add the domain to a hosting plan in your panel, or as DNS Only.

    Nothing is copied when the nameservers change: the zone at DreamHost starts with what you add.

  2. 2At the domain's registrar

    Recreate the records you keep (email first), then set the three names at your registrar.

  3. 3The wait: the .com registry

    Wait 4 to 72 hours: DreamHost's own figure for nameserver changes.

    DreamHost says4 hr–72 hr
    .com referral TTL2 days

    “Nameserver changes can take anywhere from 4-72 hours to fully update online.”

Bars: DreamHost's own figure, and the NS TTL the .com registry gave out when we asked on October 24, 2026.

Is my domain's DNS at DreamHost?

Ask one of DreamHost's nameservers directly, with recursion off: a domain it holds comes back with the aa flag and its own SOA; one it doesn't hold gets REFUSED.

The check above does this at every DreamHost server for your domain, then compares each record with what Google and Cloudflare hand out.

What DreamHost's servers answereddig +norec +tcp · October 24, 2026
A zone it holdstocaboca.comThe zone
$ dig @ns1.dreamhost.com tocaboca.com SOA +norec +tcp
;; status: NOERROR · flags: qr aa
tocaboca.com. 300 IN SOA ns1.dreamhost.com. hostmaster.dreamhost.com. 2026101201 …
A domain it doesn't holdzq7x3k9p2m-dnsrobot-test…No zone
$ dig @ns1.dreamhost.com zq7x3k9p2m-dnsrobot-test-20261024.com SOA +norec +tcp
;; status: REFUSED · flags: qr (no aa)
;; ANSWER: 0, AUTHORITY: 0    ; NSID: hyd06

How each host says “no zone”

Recorded with dig over TCP, recursion off, on October 24, 2026. DreamHost's servers are on Cloudflare's network, so the check above asks them through a Globalping probe.

What are DreamHost's MX records?

DreamHost mail uses mx1.dreamhost.com and mx2.dreamhost.com as its MX records, and netblocks.dreamhost.com as its SPF include.

They sit in the zone wherever the domain's DNS is hosted: change the nameservers without them and mail stops. What breaks in a move

The records to copyDreamHost's help pages · October 24, 2026
DreamHost mailIf it's missing
MXmx1.dreamhost.commx2.dreamhost.comIf it's missing: mail can't reach the mailboxes
TXTv=spf1 mx include:netblocks.dreamhost.com include:relay.mailchannels.net -allIf it's missing: its mail fails SPF checks

help.dreamhost.com

How to check if a website is hosted on DreamHost

Look at the site's address, not its nameservers: DreamHost's websites run on AS26347, while its nameservers answer from Cloudflare (AS13335).

So a domain can use DreamHost's DNS and be hosted elsewhere, or the other way round. The Hosting Checker reads the address, nameservers, CNAME and headers together.

One domain, two networks: tocaboca.comTeam Cymru · October 24, 2026
tocaboca.com
NS
Nameserversns1–3.dreamhost.comAS13335 Cloudflare
A
Website3.175.34.33 · 3.175.34.119AS16509 Amazon.com, Inc.not in DreamHost's hosting networks: this site is hosted elsewhere

DreamHost's address spaceRIPEstat · September 25, 2026

AS26347DREAMHOST-AS

New Dream Network, LLC · ARIN · since 2002

182,528

IPv4 addresses · 24 prefixes · 3 IPv6 prefixes
69.163.128.0/17173.236.128.0/1767.205.0.0/18
  • AddressAS26347
  • NS*.dreamhost.com
  • CNAME—
  • Headers—
  • Check a site at DreamHostHosting Checker
Routing data from RIPEstat, September 25, 2026; signals from the Hosting Checker's registry.

DreamHost nameservers: FAQ

What are DreamHost's nameservers?

DreamHost's nameservers are ns1.dreamhost.com, ns2.dreamhost.com, and ns3.dreamhost.com. Point a domain there at its registrar, after adding the domain to your DreamHost account, then check the zone on this page before you switch. Every DreamHost-managed domain uses these three names; a registrar normally needs only the names, not the addresses.

How do I change my nameservers to DreamHost?

Add the domain to a hosting plan in your panel, or as DNS Only. Recreate the records you keep (email first), then set the three names at your registrar. Wait 4 to 72 hours: DreamHost's own figure for nameserver changes. Then check the zone with the tool on this page before you switch.

How long does a nameserver change to DreamHost take?

DreamHost says 4 hours to 72 hours. The real bound is the registry's NS TTL: the .com registry hands out a delegation for 2 days, so some resolvers keep asking the old nameservers that long. Keep the old host's zone answering until then, and compare both zones before deleting anything.

Can I use DreamHost's DNS without its hosting?

Yes. A domain can be added as DNS Only, which keeps its custom records and email, and an account whose only domain is DNS Only needs no hosting plan. Point the domain's nameservers to the ones DreamHost gives you, then add the records your site and mail need, since the new zone starts empty. Check it on this page before you switch.

Does DreamHost support DNSSEC?

Not on its nameservers: a domain that uses DreamHost's DNS can't be signed. Turn DNSSEC off at the registrar before you point the domain to DreamHost, or validating resolvers will reject every answer. DreamHost offers DNSSEC only as a registrar, with a third-party DNS host, and not for .eu domains.

What are DreamHost's MX records?

DreamHost mail uses mx1.dreamhost.com and mx2.dreamhost.com, with the SPF include netblocks.dreamhost.com. They belong in the zone wherever the domain's DNS is hosted, so add them at the new host before you move the nameservers away from DreamHost, or mail stops reaching the mailboxes.

Is a site hosted on DreamHost if it uses DreamHost's nameservers?

Not necessarily: nameservers say where the DNS is, not the website. DreamHost's nameservers answer from Cloudflare (AS13335), while its web servers are on AS26347. Look up the site's address, or run the Hosting Checker, which matches the address, nameservers, CNAME and headers.

Why is DreamHost checked through Globalping?

DreamHost's nameservers are on Cloudflare's network (AS13335), and our checks run on Cloudflare Workers, which can't open a DNS connection to it. So your browser asks a Globalping probe to send the query, recursion off, and the result names the probe's city and network. An authoritative answer is the same whoever asks.

Does changing nameservers to DreamHost move my email?

Yes, it moves every DNS record. DreamHost warns that records kept at the old host, such as email, stop working unless you recreate them in the DreamHost panel first. To keep mail where it is, copy its MX and SPF records into DreamHost before the switch, or change only individual A records instead of the nameservers.

Why are DreamHost's MX records sometimes mx1.mailchannels.net?

With DreamHost's spam filtering on, its MX records appear as mx1 and mx2.mailchannels.net; with it off, as mx1 and mx2.dreamhost.com. Its default SPF record covers both, through include:netblocks.dreamhost.com and include:relay.mailchannels.net, and adding a custom SPF record removes that default, so copy both includes into your own.

Other hosts' nameservers

The 13 hosts this check asks, by how many of 4,000 sampled websites use their nameservers.

Sites on each host's nameservers4,000 sites, Tranco ranks 20,001–600,000
  1. GoDaddynsNN.domaincontrol.comA pair per account140
  2. Namecheapdns1 + dns2.registrar-servers.comSeveral sets43
  3. OVHcloudnsNN + dnsNN.ovh.netA pair per domain27
  4. Hostingername.dns-parking.comA pair per site19
  5. IONOSns1ZZZ.ui-dns.de / .biz / .org / .comA set of four per domain16
  6. SiteGroundns1 + ns2.siteground.net9
  7. DreamHostthis pagens1–3.dreamhost.com6
  8. HostGatornsN · cnsN.hostgator.comA pair per hosting plan4
  9. Bluehostns1 + ns2.bluehost.com3
  10. Hosting.comns1–4.stableserver.net3
  11. 20ins1–4.stackdns.com2
  12. Squarespaceconnect1 + connect2.squarespacedns.comSeveral sets2
  13. WixnsN.wixdns.netA pair per account1
Nameservers read through 1.1.1.1 for 4,000 random sites of the Tranco list; each row opens that host's page.

Missing something?Suggest a feature or a new tool

Related tools