I know that there are going to be several ways to make this happen, but I need to make this specific thing happen for a client:
Client has a website on siteworx server_a.com called client.com
Client has a website on siteworx server_b.com called other.client.com
I need to get tinydns on server_a to subdomain forward to server_b for the subdomain other.client.com. Specifically, I think that I need to add the tinydns DATA record:
My first thought was to edit the dns records for client.com under nodeworx on server_a.com. I thought that I would add an NS record that looked like this:
Dave, I think all you need to do is create a DNS “A” record on server_a for other.client.com, and point it to the IP address that domain uses on server_b.
work, but what I have been asked to do is set up a true DNS delegated subdomain environment that gives all of the subdomains autonomous dns capability. For example, imagine…
The same would be true for es.big.com except Sammy would be their administrator. Now Harvey and Sammy never got along and they didn’t trust one another. So, we have to give them separate but equal admin capabilities and keep them off of the same machine. (you get the idea…)
I just don’t know how to get that done through nodeworx or manually in a way that won’t be backed out at the next reboot. (I don’t mind using phpmyadmin if I have to.)
I know it’s Christmas season and everyone has a ton of stuff to do. So, don’t knock yourself out on this one. It’s something that I really want to do entirely in the Nodeworx/Siteworx environment, but in the spirit of “make it work now” I have used one of our old bind-based DNS servers to act as the “root” server for the domain and used it to delegate the subdomains to the Nodeworx tinydns servers.
Just give me a “heads up” when you work it out and have a very happy holidays!