Not too soon.. as usual.When 1.62.9 coming ?![]()
I'm not native English, so I'm not sure if I understand you correctly. But a reseller can have is own nameservers. I don't see any issue there.though DA offered reseller accounts but they didn’t allow private / white label name servers for resellers ?
I'm almost there I think.Hope I make sense.
It's not a workaround, it's rather default for years like this. Not many hosters are using so many nameservers and even if they do, if hey all have different geo locations as should be. Because otherwise I wouldn't know why so many were needed. But that's a personal question.I think instead of doing workarounds, directadmin should work quickly add such functionality.
https://help.directadmin.com/item.php?id=283So this means though DA offered reseller accounts but they didn’t allow private / white label name servers for resellers ? Weird.
The locations in DirectAdmin where the NS records will be used, are specified at:
All of these settings ultimately end up changing just the NS records of a domain, so by changing the NS values manually, that's all that really matters.
- Admin Level -> Admin Settings -> ns1/ns2: The main nameservers for the box. Use to give to new Admins and Resellers, and for fallback values. The IPs that these resolve to are the IPs used for "virtual" nameservers at the Reseller Level.
- Reeller Level -> Nameservers -> ns1/ns2 (bottom set): The default values that are given to newly created Users created by this Reseller.
As an "Admin", these values will be given to a new Reseller if "personal dns" is not enabled.- Reseller Level -> List Users -> username -> ns1/ns2: The default values that are given to newly created domains by the User.