https://github.com/mark-ignacio/tailscale2cloudflare

Don't want to use MagicDNS? Put all of those DNS entries in Cloudflare instead.
https://github.com/mark-ignacio/tailscale2cloudflare

cloudflare go tailscale

Last synced: 3 months ago
JSON representation

Don't want to use MagicDNS? Put all of those DNS entries in Cloudflare instead.

• Host: GitHub
• URL: https://github.com/mark-ignacio/tailscale2cloudflare
• Owner: mark-ignacio
• License: apache-2.0
• Created: 2021-05-08T15:02:28.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2024-06-28T02:00:14.000Z (7 months ago)
• Last Synced: 2024-08-02T15:48:01.773Z (6 months ago)
• Topics: cloudflare, go, tailscale
• Language: Go
• Homepage:
• Size: 86.9 KB
• Stars: 21
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# tailscale2cloudflare

A tiny utility to run periodically that updates DNS entries for your Tailscale devices in a Cloudflare zone. It's currently being used to keep a globally-distributed K3S cluster running.

It can(not):

- [x] Create A records based on Tailscale hostnames

- [ ] Update existing A records

- [x] Support subdomain suffixes

- [ ] Support multiple A records for a host

`grep -F TODO` to see the various complicated things that need to be done.

## Note on hostnames, machine names

Per https://github.com/mark-ignacio/tailscale2cloudflare/issues/2, it's possible to have a device hostname that isn't a valid DNS name. 

As of 07/18/2022, tailscale2cloudflare has switched to using [machine names](https://tailscale.com/kb/1098/machine-names/), which parallels Tailscale's MagicDNS implementation. To retain the old behavior of using hostnames, use the `--sync-hostnames` flag or set `SYNC_HOSTNAMES=1`.