External-dns interfacing to Route 53


When using the external-dns service to populate AWS Route 53 records, is it possible to change the name of the record set from :




If so, how please



No this is not possible to change the fqdn as you could have multiple services with the same name and Rancher wouldn’t know which service to route to.

This is the reason that the fqdn contains stackName and environmentName.

I see, but that leaves the users with a very unfriendly URL to use ( and remember )

Any thoughts on how to get around this ?

Can I get onto the external-dns container to patch the code for example (in my own deployment of course) ?

I have also been wanting to change this.

Our preference would be to have something like this:

I actually tried to fork the external-dns repo for this and change the code creating the fqdn - which was quite easy. I have then build But for some reason the stack is not starting up properly when the containers are deployed. Might be something “fgo” specific I am not doing before building my container.

The ideal solution would be to have various supported options available in the official image.

As far as I can see, having stackname.zoneName should be ok - as all stacks have the be uniquely named.

It would also be great if this kind of functionality was included in the Rancher load balancers, so that you get service dynamic discovery with configurable fdqdn names for the load balancer to handle.

1 Like