Member Avatar for S Rehman

This question is not pertaining to the development. It is rather deployment question.

My client has bought another domain name and his provider is not sharing its user id and password. they asked me to share my name server. Is it safe to share my hosting account name server so that he can propagate the domain name to my hosting account.

  • 3 Contributors
  • 2 Replies
  • 605 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by rch1231

Dani AI

Generated

Short answer: sharing just the nameserver hostnames (for example ns1.hosting.com, ns2.hosting.com) is normally safe — those hostnames are public and do not by themselves give someone your control‑panel login or file access. The important distinction is between giving a nameserver name (a DNS destination) and giving account credentials or zone‑editing rights. , and already touched on the visibility/testing side; below is a practical checklist and some safer alternatives.

  • Prepare the zone first: add the new domain in your hosting DNS panel and create the required records (root A, www, MX, SPF/DKIM if needed). Don’t let the registrar switch NS before the zone exists — that causes downtime.
  • Use a short TTL while switching (e.g., 300s) to speed propagation, then raise it back after things stabilize.
  • Share only the authoritative NS hostnames; never share control‑panel or FTP credentials. If the registrar/provider needs to do the change for the client, give them the NS list and confirm they applied it.
  • Verify mail and subdomains (MX, TXT, CNAME) — simply changing NS doesn’t automatically create those records.
  • If you don’t want ongoing DNS responsibility, ask the registrar/provider to add A/CNAME records to point to your host IP, or move DNS to a third‑party DNS service that allows delegated access.

Quick checks you can run after the registrar updates delegation:

dig NS example.com +short
dig @ns1.yourhost.com example.com A +short
dig MX example.com +short

Final cautions: never share logins; if multiple clients will point to your DNS long‑term, consider a DNS‑only account or a managed DNS service so you can grant limited access and avoid mixing hosting credentials with DNS administration. If anything seems unclear, confirm the exact steps the registrar/provider will take and test before the cutover.

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

For support I often have to know this to test the name server and then compare results to other name servers.

In this case this information is needed to propagate details. So another good reason to share.

Now how do you explain to folk that I can't exploit your PC's IP address of 192.168.0.10?

Member Avatar for rch1231

Your name server are available on the internet anyway. If you are on a system with whois installed (rwhois) then you can enter

whois <domainname>

And you get all of the information about that domain including who owns it, the registrar, and what the primary name servers are. You can get the same information from any of the whois sites out on the internet.

Edited by rch1231 because: misspelled word
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.