Tunnel to multiple domains adds wrong CNAME

Zero Trust Cloudflare Tunnel
1

What is the name of the domain?

cv.example.tech

What is the issue you’re encountering

When routing the ingress rule of another domain, the domain is pre-added to the other domain instead

What are the steps to reproduce the issue?

  • Have two domains in the account, i.e., example.tech and example.space
  • Add ingress rules for multiple service.example.tech in the config.yml file
  • Add an ingress rule for the service.example.space in the config.yml.file
  • Run cloudflared tunnel route dns tunnelname service.example.space

The cloudflared service will add a new cname at service.example.space.example.tech instead!

2

How did you setup your tunnel? May I ask if you’re adding new hostnames via Zero Trust dashboard or manually via config.yml file? :thinking:

3

I’m manually configuring my config.yml file. The configuration looks like this:


tunnel: <tunnel-id>
credentials-file: credentials.json

ingress:
- hostname: service1.example.tech
  service: http://localhost:8118

- hostname: service2.example.tech
  service: ssh://localhost:22

[...]
# These are the problematic ones

- hostname: service.example.tech
  service: http://localhost:5001

- hostname: service.example.space
  service: http://localhost:5001

[...]
# Catch-all rule
- service: http_status:404

I know that I could manually configure everything from the dashboard; however, I have some automatic routine to setup new services, and my workflow involve configuring the config.yml file locally.

4

Thank you for feedback.

And the rules are valid “as-is” when they’re configured and added via your workflow implementation, when you run cloudflared tunnel ingress validate, correct? :thinking: Except you get this sub-sub domain CNAME record, somehow added …