[GH-ISSUE #54] Allow any value for gossip protocol DNS discovery domain #48

New issue

Open

opened 2026-03-02 23:02:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 23:02:00 +03:00

Owner

Originally created by @mkjpryor on GitHub (Jul 5, 2021).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/54

Currently, the gossip_dns_host is derived from the FLY_APP_NAME environment variable.

This makes it almost impossible to use the gossip protocol in an environment other than Fly, despite the implementation being pretty generic and only requiring DNS.

By allowing the gossip_dns_host to be specified in full and falling back to the current derivation from FLY_APP_NAME, it should allow other implementations of a distributed system. For instance, headless services in Kubernetes could be used to facilitate the gossip protocol.

Originally created by @mkjpryor on GitHub (Jul 5, 2021). Original GitHub issue: https://github.com/agrinman/tunnelto/issues/54 Currently, the `gossip_dns_host` is derived from the `FLY_APP_NAME` environment variable. This makes it almost impossible to use the gossip protocol in an environment other than Fly, despite the implementation being pretty generic and only requiring DNS. By allowing the `gossip_dns_host` to be specified in full and falling back to the current derivation from `FLY_APP_NAME`, it should allow other implementations of a distributed system. For instance, headless services in Kubernetes could be used to facilitate the gossip protocol.

kerem commented

2026-03-02 23:02:01 +03:00

Author

Owner

@agrinman commented on GitHub (Jul 5, 2021):

Yes I agree, happy to take a look at any PRs for this

@agrinman commented on GitHub (Jul 5, 2021): Yes I agree, happy to take a look at any PRs for this