Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
infrastructure:network:tailscale [2022/08/08 12:52] – maff | infrastructure:network:tailscale [2022/08/08 15:43] (current) – maff | ||
---|---|---|---|
Line 30: | Line 30: | ||
* Maybe just use a tailscale-aware load balancer and stick with good old DNS for service ID? | * Maybe just use a tailscale-aware load balancer and stick with good old DNS for service ID? | ||
* Get DNS working properly (maybe write a script/ | * Get DNS working properly (maybe write a script/ | ||
+ | * Idea for a science-based naming system (SBNS) (listen to Kill James Bond!) | ||
+ | * TLD .tail | ||
+ | * tag.tail - returns A and AAAA records for all hosts with the given tag | ||
+ | * hostname.tail - returns A and AAAA for a host | ||
+ | * hostname.tag.tail - as with hostname.tail - might be useful if two hosts have the same name? does TS allow that? | ||
+ | * service.tail - it'd be cool to have some kind of declarative thing so you can say like, grafana.tail and it goes to a web loadbalancer for grafana somewhere on your tailnet, though that's more of a consul thing i guess | ||
+ | * DNS resolution is working over TS. | ||
+ | * Because I run AdGuard Home inside docker using macvlan, i would have to have ran tailscale inside the AGH container in order to do it " | ||
+ | * AGH has an internal address used for host-to-container resolution because traffic can't go from a host to a macvlan' | ||
+ | |||
+ | <code - iptables-save output> | ||
+ | -A PREROUTING -i tailscale+ -p udp -m udp --dport 53 -j DNAT --to-destination 172.21.0.53 | ||
+ | -A PREROUTING -i tailscale+ -p tcp -m tcp --dport 53 -j DNAT --to-destination 172.21.0.53 | ||
+ | -A POSTROUTING -s 172.21.0.53/ | ||
+ | </ | ||
+ | |||
* VoIP! | * VoIP! | ||