# Ingressroute subdomain rule

**URL:** <https://community.traefik.io/t/ingressroute-subdomain-rule/17919>\
**Category:** Traefik v2\
**Tags:** kubernetes-ingress\
**Created:** [March 14, 2023, 1:53pm UTC](https://community.traefik.io/t/ingressroute-subdomain-rule/17919 "2023-03-14T13:53:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kingisch](https://avatars.discourse-cdn.com/v4/letter/k/bc8723/32.png) [@kingisch](https://community.traefik.io/u/kingisch)\
**Post date:** [March 14, 2023, 1:53pm UTC](https://community.traefik.io/t/ingressroute-subdomain-rule/17919/1 "2023-03-14T13:53:03Z")

</div>

Hi there,

I am quite new with kubernetes and Ingressroutes and am facing the following challenge:

I wanted to make a pod (zigbee2mqtt) available through a subdomain. Already tried it with pathprefix but it was not working so I thought about subdomains with the following IngressRoute forwarding to the respective k8s service: [http://zigbee.domain.home](http://zigbee.domain.home)

```auto
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: zigbee2mqtt-ingress-route
  namespace: homeassistant
  labels:
    app: zigbee2mqtt
spec:
  entryPoints:
    - web
  routes:
  - match: HostRegexp(`zigbee.domain.home`) 
    kind: Rule
    services:
    - name: zigbee2mqtt
      port: 8080
      kind: Service
  tls: {}

```

It shows up in the Traefik dashboard but, however, does not lead to the connected service:

 ![grafik](https://us1.discourse-cdn.com/flex020/uploads/containo/original/2X/e/ed231da14264555e09d9e66809285266b253cdd9.png)

Entering the service's IP directly (red) works. The domain (blue) is also internally registered as a DNS entry.

Any ideas what I am missing?  
Thanks and looking forward to learning a lot 🙂