Best Practices for 
Name Servers





icon Best Practices for Name Servers

 Best Practices Best Practices for Name Servers


You can list multiple nameservers, but you cannot mix nameservers from different providers (like Cloudflare, Google DNS, or a custom DNS service) for a single domain — doing so will likely break DNS resolution or cause inconsistent behavior. 

 Key Points:  

✅ What you can do: Use multiple nameservers from the same DNS provider (e.g., ns0.makeyournetwork.com.com and  ns2.makeyournetwork.com are both from Makeyournetwork). Most DNS providers give you 2–4 nameservers to configure for redundancy and reliability.

❌ What you cannot do: You cannot mix: *.ns.cloudflare.com (Cloudflare) dns.google.com (Google Public DNS) dns.makeyournetwork.com (Custom provider) DNS for a domain must be delegated to a single authoritative provider, not several. What to do instead: If you want features from multiple DNS services (e.g., Google DNS’s speed + Cloudflare’s DDoS protection), here are your options: Use Cloudflare as your authoritative DNS, and configure records (like A, CNAME, etc.) within Cloudflare. Use Google Public DNS as a resolver, but this is for end users — not for setting on your domain registrar. For custom records or integrations, see if Cloudflare or your main provider supports forwarding or proxying.

✅ Example of a valid nameserver setup:  nitin.ns.cloudflare.com vera.ns.cloudflare.com

❌ Invalid setup (do not do this):  

  • nitin.ns.cloudflare.com ← Cloudflare
  • dns.makleyournetwork.com ← custom DNS 
  • dns.google.com ← Google DNS