# Can I specify multiple advertisedHost values under linkListeners.transport?

**URL:** <https://openziti.discourse.group/t/can-i-specify-multiple-advertisedhost-values-under-linklisteners-transport/4480>\
**Category:** Uncategorized\
**Created:** [May 5, 2025, 12:54am UTC](https://openziti.discourse.group/t/can-i-specify-multiple-advertisedhost-values-under-linklisteners-transport/4480 "2025-05-05T00:54:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![am3y](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/am3y/32/2366_2.png) [@am3y](https://openziti.discourse.group/u/am3y)\
**Post date:** [May 5, 2025, 12:54am UTC](https://openziti.discourse.group/t/can-i-specify-multiple-advertisedhost-values-under-linklisteners-transport/4480/1 "2025-05-05T00:54:24Z")

</div>

Hi everyone,

I’m deploying OpenZiti routers in a multi-cloud mesh (AWS + OVH), and I’d like each router to accept link-dial connections on both its internal cluster name and a public DNS name. In my `values.yaml`, I currently have:

```yaml
linkListeners:
  transport:
    enabled: true
    containerPort: 3022
    advertisedHost: router1.example.com
    advertisedPort: 3022
    …

```

It looks like I can only set **one** `advertisedHost`.  
**1. Is there any way to provide multiple `advertisedHost` entries** so that the same transport listener responds on, say, `router1.internal.local` _and_ `router1.public.example.com`?

**2. If multiple hosts aren’t supported** , are there any recommended patterns or workarounds to achieve the same outcome?

Any advice or pointers would be hugely appreciated. Thanks in advance!

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [May 5, 2025, 2:02pm UTC](https://openziti.discourse.group/t/can-i-specify-multiple-advertisedhost-values-under-linklisteners-transport/4480/2 "2025-05-05T14:02:37Z")

</div>

You should be able to declare a second listener

for example I have two ports listening:

```auto
link:
  dialers:
    - binding: transport
  listeners:
    - binding: transport
      bind: tls:0.0.0.0:10080
      advertise: tls:ec2-3-18-113-172.us-east-2.compute.amazonaws.com:10080
      options:
        outQueueSize: 4

    - binding: transport
      bind: tls:0.0.0.0:20080
      advertise: tls:ec2-3-18-113-172.us-east-2.compute.amazonaws.com:20080
      options:
        outQueueSize: 4

```

And the listeners

```auto
LISTEN 0 4096 *:10080 *:* users:(("ziti",pid=222054,fd=7))
LISTEN 0 4096 *:20080 *:* users:(("ziti",pid=222054,fd=8))

```

---

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [May 5, 2025, 2:56pm UTC](https://openziti.discourse.group/t/can-i-specify-multiple-advertisedhost-values-under-linklisteners-transport/4480/3 "2025-05-05T14:56:27Z")

</div>

Since you're deploying the router to Kubernetes, you can specify additional edge listeners in `edge.additionalListeners` ([Install the Router in Kubernetes | OpenZiti](https://openziti.io/docs/guides/deployments/kubernetes/kubernetes-router#additional-listeners-and-volumes)) and I've just added experimental support for `linkListeners.additionalListeners` (optional, additional link bindings) with associated k8s cluster services and optional ingresses in this draft pull request which you may preview: [configure router with additional link bindings by qrkourier · Pull Request #336 · openziti/helm-charts · GitHub](https://github.com/openziti/helm-charts/pull/336)

I won't have time to test it today but please let me know if you do!