-
Notifications
You must be signed in to change notification settings - Fork 66
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
Creating DNSEntry to create A record in Route53 Hosted Zone with 1 dnsname target. #371
Comments
If you are using a AWS Route 53 hosted zone and the target is a Amazon load balancer name, an
The dns-controller-manager must lookup the IP address of the targets periodically and updates the DNS record if needed. |
By Amazon load balancer name, do you mean the value of "dns.gardener.cloud/dnsnames:" key in the kubernetes Service resource? Or the value of We set the value of "dns.gardener.cloud/dnsnames:" in the target of DNSEntry. But it created a CNAME record. We need to have an There is an external Routing from a CNAME record that targets the ´dnsName´of the So, we need to create an A record. |
All AWS application and classical load balancers with domains ending e.g. with
Thanks for providing more details. But I think it is out of scope of the dns-controller-manager. As already mentioned the feature for multiple targets is only a work around as there is no DNS record like We can not give any guarantees about the IP lookup, especially which DNS servers are used. |
What would you like to be added:
Creating
A
DNSRecord with DNSEntry with 1 target with DNSname.Why is this needed:
If I understand it correctly, to create a A record in Route53 HostedZone, the DNSEntry needs to have IP as target
or have multiple DNS name as target:
And to create a CNAME record, the DNSEntry must have a single DNS name is in the target.
Currently to force create an A record, we are adding a subdomain as target:
This creates an A record. But in the end we see 1 IP as target as expected.
Is there any way to have 1 dnsname as target and create an A record? If its not possible, we would like to request a feature to enable us create an A record from DNSEntry with a single dnsname target.
The text was updated successfully, but these errors were encountered: