Quote:
Originally Posted by eth00
Why are you even having a client using 3rd party nameservers use your server first? That eliminates all gains you might have and makes it worse off then just using your own. At least that is what I think I understand from your question.
What I would do is setup 2 additional nameservers that are the IPs of 3rd party dns servers. Then if clients want some other dns servers just manually assign them.
|
I quite agree with your question.
I made it clear to my host that clients weren't looking to use the 3rd party as secondary nameservers but as primary - that is, if a client used easydns.com,
all their authoritative nameservers would be that of easydns.com, not my private nameservers at all.
Here is the final set up my host suggested:
Quote:
- Clients hosting on my VPS but using a third-party DNS service don't need a DNS zone on the VPS at all because my nameservers are not authoritative for their domain(s).
- Clients using third-party DNS would need to set up their DNS zone with the third-party provider and point to those third-party nameservers at their domain registrar.
- If it's a new client, the DNS zone automatically created for the account by WHM needs to be deleted. Instead, the DNS zone needs to be created at the third-party DNS provider.
- If it's an existing client switching to third-party DNS, their DNS zone also needs to be deleted from the VPS (of course, after pointing to third-party at their registrar and creating their zone file with the provider)
- If the VPS hosts clients using private nameservers (mybusinessdomain.com) and 3rd party nameservers, then, resolver IPs are required in /etc/resolv.conf. If all the clients on the VPS use 3rd party nameservers, no resolver IPs are required in /etc/resolv.conf because it uses those nameservers to do its own lookups (the private nameservers)
|
I hope this helps anyone else looking for a similar solution.