# AWS Route53 Catalog

**URL:** <https://forums.suse.com/t/aws-route53-catalog/3293>\
**Category:** Rancher 1.x\
**Created:** [July 3, 2016, 3:31pm UTC](https://forums.suse.com/t/aws-route53-catalog/3293 "2016-07-03T15:31:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![upbeta01](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/upbeta01/32/1463_2.png) [@upbeta01](https://forums.suse.com/u/upbeta01)\
**Post date:** [July 3, 2016, 3:31pm UTC](https://forums.suse.com/t/aws-route53-catalog/3293/1 "2016-07-03T15:31:55Z")

</div>

I Tried AWS Route53 (External DNS) from Rancher’s Catalog and noticed that the service “assumable” is for Route53 alone, calls other DNS providers (in rancher catalog)…

Is this normal? Why would a catalog dedicated for Route53, be calling other provider’s API?

 ![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/b/b39acf12cb08a03fe89a51e228186ea018ea142b.png)

---

<div class="post-metadata">

**Author:** ![upbeta01](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/upbeta01/32/1463_2.png) [@upbeta01](https://forums.suse.com/u/upbeta01)\
**Post date:** [July 4, 2016, 12:43am UTC](https://forums.suse.com/t/aws-route53-catalog/3293/2 "2016-07-04T00:43:01Z")

</div>

UPDATE: Just got a conversation with Darren about this and was confirmed that it’s only reading env file but not querying any external endpoints.

![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/b/b115de626334bc548de33847e48d42a0de02c075.png)