# Trying to point domain from Digital Ocean to Netlify. No domain found **URL:** \ **Category:** Support\ **Tags:** netlify-dns-https-ssl\ **Created:** [April 20, 2020, 8:47pm UTC](https://answers.netlify.com/t/trying-to-point-domain-from-digital-ocean-to-netlify-no-domain-found/12903 "2020-04-20T20:47:50Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![luke](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/luke/32/39_2.png) [@luke](https://answers.netlify.com/u/luke)\ **Post date:** [April 23, 2020, 7:08am UTC](https://answers.netlify.com/t/trying-to-point-domain-from-digital-ocean-to-netlify-no-domain-found/12903/4 "2020-04-23T07:08:09Z")
Hi, @Filament, I’m seeing that the name servers (NS records) for the Netlify DNS were added at the existing name server for this domain. Instead what is needed is for the existing domains name server to be replaced by the one for Netlify DNS. Here is a traced/recursive lookup for this domain name: ```plaintext $ dig filamentgroup.com NS +trace ; <<>> DiG 9.10.6 <<>> filamentgroup.com NS +trace ;; global options: +cmd . 86332 IN NS e.root-servers.net. . 86332 IN NS h.root-servers.net. . 86332 IN NS l.root-servers.net. . 86332 IN NS i.root-servers.net. . 86332 IN NS a.root-servers.net. . 86332 IN NS d.root-servers.net. . 86332 IN NS c.root-servers.net. . 86332 IN NS b.root-servers.net. . 86332 IN NS j.root-servers.net. . 86332 IN NS k.root-servers.net. . 86332 IN NS g.root-servers.net. . 86332 IN NS m.root-servers.net. . 86332 IN NS f.root-servers.net. . 86332 IN RRSIG NS 8 0 518400 20200505050000 20200422040000 48903 . SpOIowr6/n2bsKkr7XiRe1J5gPmH9Vt00YGzLBDZt7CPm1nDjjzxSp9V y5dRz+g0COnmbEb4WklQXRZ3aus9Qo08k0GP8rspM3/g2hHml8FR5bv0 Jvde8Y6n/bQl5+f47/dCmw84wLYbf+ziW6vrL7rwkVl1foXnKMiVjuGF r+DsduOW8S3KSPqrKCFsvIS4kWoNQKRcn9iDKPuZijC3cPhIUpIiQn4N dFHG6uSNGbb9N3Jp4LV0L/IO2jiAfIsIW+K0t7KPZtqwa6KSDri+hxf8 cESHz3AsQkICj4CuKU2R+egnADhrsiaKNVcozYofCuw6B7TKtuG9rQAz aFN4xQ== ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 18 ms com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766 com. 86400 IN RRSIG DS 8 1 86400 20200506050000 20200423040000 48903 . Enqd4bffSJHlv8mqHcAptS9+fHo3cg6vCIQgrOZ3aBfx2nG4CjS27iEG 6u6NsPfcKVrz7RoU2xDtDMNJOcMBJdJe/lGNeo14N69SM0/MV2Z8wZBD HRPd2Y8Z1nyc7EnDbkFzuWV5G6vafaQa4KTQpG6jGOPIQpYESNiinxfy 0QQWUJELvjSOideCPqQcug2P2Pln7BzWiqFSg6I8d1h44349LsXcbr5W zJwZQJKLoDd0ysyGl5Bq3UZgfWYvTJFmmZ/OwKYT4QQ4BE0MtbVwae8X 9yI6d9jENsz+eebEEtxLt6o/LNQb3PdNhUH1PC1pxfHiEiNyYUcvbJdf Flgntg== ;; Received 1177 bytes from 198.97.190.53#53(h.root-servers.net) in 54 ms filamentgroup.com. 172800 IN NS ns1.digitalocean.com. filamentgroup.com. 172800 IN NS ns2.digitalocean.com. filamentgroup.com. 172800 IN NS ns3.digitalocean.com. CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20200427045033 20200420034033 39844 com. BDAWMm4AsSRfrBwOXhNN8ihw++J2UkhEk8A6LeSIz1llDs5kt0CcOqTM OK1txlQNr3N0k1RTBW/hkEZ1mxjIHF2GARt/hpO43ILPBVs/vhKAKCKh A96XJG+NzN0t/heB6mFNASKAcmVdfT5a0tVkmmzhGktDp5ECdZAIFRhZ 8y6jxsUhGP7ZiN1AfFBi1cWeSth5FW4Btpy9RffVKg5lIA== 2M9RNRC69I3OHAKUNVJTPP58J1CG4QA5.com. 86400 IN NSEC3 1 1 0 - 2M9SHNCAUFDR50JIKFIFVDGUKJR2BSM8 NS DS RRSIG 2M9RNRC69I3OHAKUNVJTPP58J1CG4QA5.com. 86400 IN RRSIG NSEC3 8 2 86400 20200429055718 20200422044718 39844 com. o2Zge2ojBtIXhrz827GNX2dj9Z8jW9FPeCobdx6sJyMjrquZXWl72Gpn LwOpc7MPVLdpckGVo2Qu1WgO/JjK6gRkOLu/9oWbPW0wjDlJU/vY+7dr bfCCIi3Uhkgh3P8wjvhVTB0SElXZgPcu9ggxWV1k+104Q0xw7cIzB44u ZWUgIvWnmJortPhPvl94I+C7HjFgCM86GuRn2StNCbNojA== ;; Received 794 bytes from 192.48.79.30#53(j.gtld-servers.net) in 58 ms filamentgroup.com. 1800 IN NS dns1.p03.nsone.net. filamentgroup.com. 1800 IN NS dns2.p03.nsone.net. filamentgroup.com. 1800 IN NS dns4.p03.nsone.net. filamentgroup.com. 1800 IN NS dns3.p03.nsone.net. ;; Received 135 bytes from 198.41.222.173#53(ns3.digitalocean.com) in 33 ms ``` You can ignore everything above the `ns1.digitalocean.com.` lines. What this shows is that the name servers for the domain are these name servers: ```plaintext filamentgroup.com. 172800 IN NS ns1.digitalocean.com. filamentgroup.com. 172800 IN NS ns2.digitalocean.com. filamentgroup.com. 172800 IN NS ns3.digitalocean.com. ``` If you ask those servers what the name servers for the domain are they will say the Netlify DNS name servers but, in reality, those name servers won’t ever be used because that isn’t the way DNS works. Another way to see this is to check the WHOIS records for the domain: ```plaintext $ whois filamentgroup.com | egrep "^Name Server" Name Server: ns1.digitalocean.com Name Server: ns2.digitalocean.com Name Server: ns3.digitalocean.com ``` It looks like this domain is registered via [tucows.com](http://tucows.com). If so, you most likely need to be updating the name servers there (Tucows) and not at DigitalOcean. Also, before moving to Netlify DNS, please make sure to copy all of your DNS records to Netlify before doing so. There is more about there here: > [@\[Support Guide\] How do I migrate a domain to Netlify DNS with zero downtime?](https://answers.netlify.com/t/common-issue-how-do-i-migrate-a-domain-to-netlify-managed-dns-with-zero-downtime/3397): > > Last reviewed by Netlify Support - July 2025 IMPORTANT UPDATE While many details in this support guide remain valuable information, the best guide for a zero downtime DNS migration can be found here: However, there is still great information below and our support team will continue to link people to sub-sections of this support guide when they are relevant to someone’s particular situation or question. What is this topic about? This topic covers copying your existing DNS records from your c… If there are other questions about changing the DNS name servers, please let us know. --- _[View the full topic](https://answers.netlify.com/t/trying-to-point-domain-from-digital-ocean-to-netlify-no-domain-found/12903)._