We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am curious whether the config files for both of these could be merged into something like ALL.talent.c4nada.ca.yaml:
ALL.talent.c4nada.ca.yaml
talent.c4nada.ca.yaml
go.talent.c4nada.ca.yaml
https://github.com/g0v-network/domains/tree/main/c4nada.ca.domain
This would allow all the config to exist at one url, accessible at some shortlink like https://go.talent.c4nada.ca/dns
Also, ownership/maintainership metadata could be assumed as encompassing all child DNS records. (instead of repeating for each sub-node)
Just need to test it out.
The text was updated successfully, but these errors were encountered:
Confirmed that this file can be loaded up with any keys for any subdomains, and it's arbitrary.
Will leave this open to document this as an option.
Sorry, something went wrong.
No branches or pull requests
I am curious whether the config files for both of these could be merged into something like
ALL.talent.c4nada.ca.yaml
:talent.c4nada.ca.yaml
go.talent.c4nada.ca.yaml
https://github.com/g0v-network/domains/tree/main/c4nada.ca.domain
This would allow all the config to exist at one url, accessible at some shortlink like https://go.talent.c4nada.ca/dns
Also, ownership/maintainership metadata could be assumed as encompassing all child DNS records. (instead of repeating for each sub-node)
Just need to test it out.
The text was updated successfully, but these errors were encountered: