Question

DigitalOcean's Nameservers: IP-adress?

Posted September 11, 2013 17.9k views
I'm trying to set up a host name with DigitalOcean. My domain registrar (the web interface) is not only asking for the nameservers (like ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com) but also for the IP-addresses of the nameservers. Where can I find them? Thank's!
Add a comment
mail181720
By:
mail181720

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
6 answers
cohan September 11, 2013
At this current point in time they are as follows:

ns1.digitalocean.com has address 198.199.120.125
ns2.digitalocean.com has address 141.0.170.89
ns3.digitalocean.com has address 198.199.95.114

For future reference you can use the "host" command on your droplet to find the IP of a hostname (and a hostname of an IP, if there is one):

e.g. host ns1.digitalocean.com

[user@webserver ~]$ host ns1.digitalocean.com
ns1.digitalocean.com has address 198.199.120.125
Reply Report
unitydigital April 7, 2020

Short answer

DNS IP
ns1.digitalocean.com 173.245.58.51
ns2.digitalocean.com 173.245.59.41
ns3.digitalocean.com 198.41.222.173

How you can get DNS IP address
On linux or macos, open terminal and ping the dns domain name:
(I am not a windows user but I guess it should be the same command through cmd)

$ ping -c 1 ns1.digitalocean.com

The output would be something like this:

PING ns1.digitalocean.com (173.245.58.51) 56(84) bytes of data.
64 bytes from ns1.digitalocean.com (173.245.58.51): icmp_seq=1 ttl=55 time=22.0 ms

--- ns1.digitalocean.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 22.077/22.077/22.077/0.000 ms

And there you have the IP address to your DNS:

ns1.digitalocean.com (173.245.58.51)
Reply Report
paullopez05 March 12, 2014
If you're doing this from a Windows machine you can open a command (dos) prompt and type:

ping ns1.digitalocean.com

this is what you should see:

Pinging ns1.digitalocean.com [198.199.120.125] with 32 bytes of data:
Reply from 198.199.120.125: bytes=32 time=133ms TTL=57
Reply from 198.199.120.125: bytes=32 time=132ms TTL=57
Reply from 198.199.120.125: bytes=32 time=131ms TTL=57
Reply from 198.199.120.125: bytes=32 time=132ms TTL=57

the same goes for ns2.digitalocean.com and ns3.digitalocean.com
Reply Report
Xpallicer March 2, 2015

Hello I found that IPS are

ns1.digitalocean.com - 173.245.59.51
ns2.digitalocean.com - 173.245.59.41

Is this okay?

Reply Report
johnathontking August 18, 2015

Remember, ns3

Reply Report
info340f6634c77 November 9, 2015

It seems that the ip’s for all of your nameservers are changing quite frequently. If so, does this mean that I have to keep checking them regularly and keep logging into my registrar to update them? My registrar requires both host and ip for each nameserver.

Reply Report
  • Figidon December 2, 2016

    Same with my registrar, a GoDaddy .nl domain. I entered the first 3 ip’s mentioned in this topic, but I guess they are outdated already.
    Also ns1.digitalocean.com - 173.245.59.51 etc is outdated “already”.

    Can anyone at DO give an indication about the frequency of these changes? For it might give me an incentive to leave the nameservers at GoDaddy, don’t feel like bringing down the server at random times due to this kind of issues.

    Reply Report
Submit an Answer

Looking for something else?

Ask a new question Search for more help