90% of people aren’t worth the time

  • 22 Posts
  • 1.25K Comments
Joined 8 个月前
cake
Cake day: 2024年11月7日

help-circle


  • Cousin Mose@lemmy.hogru.chtoRant@lemmy.sdf.orgCookie hell
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    16 小时前

    Usually I use Safari’s Hide Distracting Elements feature to remove it and move on with my day, but I’ve also got a totally overkill blocking DNS server (as well as the AdGuard browser extension).

    As an American I route my internet traffic through Switzerland so 99% of websites give me the “reject all” option.




  • My comment was kind of high level because I wasn’t sure how much you knew technically already.

    But yeah, you would unfortunately need access to the DNS server on your router and be able to add custom records. You’d additionally need a DNS server somewhere for Tailscale clients whether that’s on a Tailscale node or just on the public internet (and configure Tailscale to use it).

    I suppose a last-ditch effort would be to buy a domain and create records pointing to both the Tailscale and internal LAN IP addresses. The downside is that you’re basically making the map to your network public but at least people wouldn’t actually be able to access those internal (LAN, Tailscale) IP addresses. The benefit would be only needing to manage one set of records in one place.

    I’m really rusty on my OSI model but Avahi, NETBEUI and friends won’t work over WireGuard tunnels because those are layer 2 protocols whereas WireGuard operates at layer 3 (if I remember correctly).


  • I do exactly this by using DNS. You’ll want DNS on your home network to report back just the internal IP addresses for each host, but not the Tailscale IP addresses (that is, if you want the hostnames to work outside of Tailscale too).

    Then for Tailscale’s DNS you’d set up records for the same hostnames but return either just the Tailscale IP addresses or both. I generally do both but it’s probably better to do the former to avoid leaks outside the WireGuard tunnels (though with a subnet router that probably won’t happen anyway).

    This is much like traditional split DNS where your internal network’s DNS server is probably going to give internal IP addresses for a local web server’s hostname but a public DNS server would return a publicly routable IP address.

    Avahi is going to be a huge pain because it relies on multicast. It won’t work over Tailscale (or traditional VPN tunnels other than an OpenVPN TAP interface) without lots of fighting.