# Setting up domain and DO nameservers

**URL:** https://meta.discourse.org/t/setting-up-domain-and-do-nameservers/99542
**Category:** Self-hosting
**Created:** [October 15, 2018, 11:56am UTC](https://meta.discourse.org/t/setting-up-domain-and-do-nameservers/99542 "2018-10-15T11:56:11Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [October 15, 2018, 12:56pm UTC](https://meta.discourse.org/t/setting-up-domain-and-do-nameservers/99542/3 "2018-10-15T12:56:53Z")

</div>

> [@Umashankar\_Ankuri](#):
>
> It’s better to use Digital Ocean DNS than just using domain provider’s (ex., godaddy /namecheap) default DNS

Really? I don’t think that’s the recommended approach:

> [@Installing over DigitalOcean and Namecheap?](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598/2):
>
> You need a DNS A record for discourse.guidekeeper.com pointing to the IP address of your server. Nameservers are generally provided by the company that you purchased the domain name from, not Digital Ocean. So you likely want to change it using the DNS control panel at the place you purchased the domain name from. In the event that you are using Digital Ocean’s nameservers (but why?) then you would need to change it using the DNS control panel at Digital Ocean.

---

_[View the full topic](https://meta.discourse.org/t/setting-up-domain-and-do-nameservers/99542)._
