# Change default Rancher Route 53 behavior?

**URL:** <https://forums.suse.com/t/change-default-rancher-route-53-behavior/3912>\
**Category:** General\
**Created:** [September 7, 2016, 12:49am UTC](https://forums.suse.com/t/change-default-rancher-route-53-behavior/3912 "2016-09-07T00:49:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![natefons](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@natefons](https://forums.suse.com/u/natefons)\
**Post date:** [September 7, 2016, 12:49am UTC](https://forums.suse.com/t/change-default-rancher-route-53-behavior/3912/1 "2016-09-07T00:49:31Z")

</div>

By default, rancher r53 creates the dns records: `=<serviceName>.<stackName>.<environmentName>.<yourHostedZoneName>`

which is fine for lower level env…but for production grade, this doesnt seem to be all that user friendly. especially when you add a load balancer your fqdns becomes: `load-balancer.myapp.prod.example.com`

is there a way to specify a DNS for a specific service?

i.e for a service/stack named `my-loadbalancer.myapp`, i want the dns to be `myapp.example.com`

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [September 7, 2016, 4:34am UTC](https://forums.suse.com/t/change-default-rancher-route-53-behavior/3912/2 "2016-09-07T04:34:44Z")

</div>

The intention is that external-dns manages a single subdomain with auto-generated names, and then you can CNAME those to whatever human-friendly names you want. So you create a record for [myapp.example.com](http://myapp.example.com) CNAME [lb.myapp.prod.example.com](http://lb.myapp.prod.example.com).

This has advantages like the Rancher code can be given restricted access to only a single subdomain (and therefore can’t break unrelated potentially important things like [www.yourcompany.com](http://www.yourcompany.com)), and that you don’t need to give it multiple credentials to manage DNS entries for different domains that may live in multiple accounts and providers.