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:
other.client.com NS server_b.com
But (apparently) you can’t do that.
Any help would absolutely be received with open and loving arms!
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.
Does that make sense?
Happy holidays! Thanks for the quick reply. Hope all is well in iworx-land.
Your suggestion makes all the sense in the world if I were trying to make something like:
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…
big.com <== main company
us.big.com <== dns subdomain 1
es.big.com <== dns subdomain 2
us.big.com would have it’s own siteworx account that has (among other things)
Harvey the us.big.com siteworx administrator
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 know that tinydns us up to the task:
Take a look at the Delegation of domain dmz.example.net part of that.
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.)
Hope you can help,
I’m really glad you’re asking this question - as I’ve had the very same one, but couldn’t wield a paragraph clear enough to explain it.
My paragraphs are normally unwieldy!
I see what you’re saying now Dave, we’ll do some testing and get back to you soon.
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!