# Route53 public IP

**URL:** <https://forums.suse.com/t/route53-public-ip/1588>\
**Category:** Rancher 1.x\
**Created:** [January 31, 2016, 11:14am UTC](https://forums.suse.com/t/route53-public-ip/1588 "2016-01-31T11:14:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lee](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/lee/32/826_2.png) [@lee](https://forums.suse.com/u/lee)\
**Post date:** [January 31, 2016, 11:14am UTC](https://forums.suse.com/t/route53-public-ip/1588/1 "2016-01-31T11:14:09Z")

</div>

I’m trying to use the Route53 service to create a DNS entry for my port 80/443 entry point LB.

The entry is being added correctly, however, it’s using my VPC IP (172.x.x.x) and not a publicly addressable one.

How can I point it to the public IP?

---

<div class="post-metadata">

**Author:** ![lee](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/lee/32/826_2.png) [@lee](https://forums.suse.com/u/lee)\
**Post date:** [January 31, 2016, 11:19am UTC](https://forums.suse.com/t/route53-public-ip/1588/2 "2016-01-31T11:19:08Z")

</div>

Actually, a more general purpose request –

I have two hosted zones for the same domain - one public, one private.

It’d be useful for the Route53 service to determine whether the zone is public or VPC - and update in _both_ zones with the public and private IPs respectively.

This is vital for AWS because certain security groups grant access based on _other_ VPC security groups, which means traffic must remain within the network to recognise it’s coming from an associated group.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [February 1, 2016, 6:59pm UTC](https://forums.suse.com/t/route53-public-ip/1588/3 "2016-02-01T18:59:06Z")

</div>

For the first issue, what IP is showing up on your host in the hosts view? Is it showing the public or private one? The Route53 service uses the IP that is shown in the host view to create records.

To update the IP of your host, you can re-run the rancher/agent command and add the `-e CATTLE_AGENT_IP=<public_ip>` to the command.

[http://docs.rancher.com/rancher/faqs/hosts/#how-does-the-host-determine-ip-address-and-how-can-i-change-it](http://docs.rancher.com/rancher/faqs/hosts/#how-does-the-host-determine-ip-address-and-how-can-i-change-it)

I’m not sure if the Route53 service would be able to handle your enhancement request but I encourage you to create an enhancement request in Github.

> **[rancher/rancher](https://github.com/rancher/rancher/issues)**
>
> Complete container management platform. Contribute to rancher/rancher development by creating an account on GitHub.