-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Feature request: support subdomains #45
Comments
I'll investigate this further after the extended weekend. This might be possible, I don't remember any limitations in the api, and checking for presence of a zone is very possible. I can look into implementing this controlled by a flag, like "default to parent domain" that can be set in the env var of the lambda function. |
FWIW, I don't think a flag is required. If subdomain exists, the expected behavior is to add subdomain records there. For reference, I am currently using the NS-records method from here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html …but my preferred use case would be to be able to choose whether or not to break subdomains out into separate zones, and have this plugin Do The Right Thing. |
I'll chat with some co-workers about this and determine if this fits the original scope of the project, I see what you're saying. While you're right, a flag isn't absolutely necessary, there needs to be some medium of control so that this script still maintains its original use-case abilities, without too many external changes, ie...needs to be a seamless change that should just integrate right into the existing uses of the script. |
Currently, I cannot create valid subdomain A records inside a parent domain:
e.g.
host.domain.tld < succeeds
host.subdomain.domain.tld < fails, despite being valid DNS
Is it possible to add A records to the parent domain (if available) when the subdomain does not exist as a separate zone?
The text was updated successfully, but these errors were encountered: