Tailscale subnet router failing DNS resolution
lucaarchidiacono
HOBBYOP

3 months ago

I recently migrated my services within an environment from EU-Netherlands to us-west2.
Services I migrated:

  • tailscale subnet router

  • cloudflare tunnel

  • nodejs apps

since the migration I‘m not able to resolve the internal app name of my nodejs apps within tailscale.

meaning I have an internal hostname:
scraper-test.railway.internal

I want to reach following endpoint:
http://scraper-test.railway.internal:8080/admin/queues

I attached, screenshots of my tailscale subnet router. I have two. One for my production env and one for my test env.

Before migrating I was able to reach my service in the netherlands region.

Solved

1 Replies

3 months ago

You can only have one subnet router active at any given time.


Status changed to Solved brody 3 months ago


Loading...