I like this idea, it would be the simplest way to keep DNS namespacing clean and is in the spirit of how DNS was originally envisioned to work. There's obviously legacy allocations that do not follow this format, and we'd have to come up with a policy to address those. CNAMEs are an option, but they will break things like MX and TXT records if I recall correctly. An alternative that I've thought of is putting the controlling call sign in a TXT record for every host in the database.
Thanks, Dan Theisen KK7OZY
On Jun 15, 2024, at 15:31, Dan Cross via 44net 44net@mailman.ampr.org wrote:
On Sat, Jun 15, 2024 at 2:41 PM pete M via 44net 44net@mailman.ampr.org wrote:
I think that using the hierarchy type of domain name is logical.
Something like hotel-dieux.ve2cbs.ampr.org where hotel-dieux is the site name ve2cbs is the club callsign and the rest is obvious.
This would be the real dns name I would use for the club I am the secretary and technical support.
But after that being said. Who would be able to control those dns? There should be a way to ID the tecnical support staff for the club call sign and those named as technical support be able to do the dns for the club.
In fact even a single user should be able to point another user as able to control the dns section of his/her allocation in case they are both sharing the same ip space for whatever reason, or the first does not know enough or understand enough to do it all.
Right now, the portal supports the concept of an organization that provides this functionality, albeit not in its fully elaborated form yet. But the ideas of multiple users associated with an organization, and assigning some sort of role-like permissions to those users, are there now.
What's missing is decoupling the idea of an organization from a specific user (I think) and allowing existing users to become affiliated with an organization, as opposed to creating new user accounts that are conceptually "owned" by the organization.
- Dan C.
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org