Hey everyone. This is probably a super noob question, but I’m very much just an amateur when it comes to self-hosting.

I host several services that I access locally through 192.whatever:####, and when I occasionally need remote access, I use Tailscale and access through 100.whatever: ####. The duplicate bookmarks is mildly annoying though.

Can I just buy a personal domain, and have all my services be coolname.com:#### for both local and Tailscale access? Is that as simple a process as I want it to be?

Edit: I appreciate all the comments and I’ll probably just use Tailacale’s MagicDNS for simplicity, but one or my (unwritten, my bad) goals was to have one URL that works locally and remotely, regardless of Tailscale. I don’t leave Tailscale constantly connected because it overheats my phone (which already has terrible battery life).

  • soratoyuki@piefed.zipOPEnglish
    1·
    1 day ago

    So this definitely seems like the easiest solution, and MagicDNS is on by default, and the normal 100… address works fine, but no combination of the short or full domain seem to actually work. Not homeserver:#### nor homeserver.tail#.ts.net:#### nor even 100.100.100.100:####. Maybe it’s an issue with Unbound or something. Blargh.

    • fuckoffplzkthx@lemmy.zipEnglish
      1·
      6 hours ago

      Not trying to sound like an ass, promise. Have you declared those routes in Tailscale? There are two methods of doing this. One uses pathing, with --set-path, and not everything supports serving on a path without changing the base URI of the application you’re trying to reach. It looks like you’re sticking to ports, but I haven’t see anyone ask how you’re declaring this with the tailscale serve command.

      And did you add a funnel, or just tailscale serve?

      tailscale funnel --bg http://localhost:1234/

      This is different, and I believe they are mutually exclusive.

      The funnel would show as https://hostname.tailnet-name.ts.net/ to anyone online without needing tailscale, and that sounds like what you’re after as far as deduplicating bookmarks. If I’m not mistaken this only supports 443/8443/10000 ports, however. It’s also hanging free in the breeze for anyone to get to if they know the URL.

      Again, sorry if this is asking redundant questions or anything.

    • FedX@quokk.auEnglish
      2·
      1 day ago

      What are you testing MagicDNS with? What are the DNS settings? What does trying dog myhost (or dig, or using about:networking in a Firfox derived browser (maybe Chrome too?) if you prefer) tell you? For reference, on a Linux host (I don’t remember exactly, so don’t quote me), you should se something like this in /etc/resolv.conf

      nameserver 127.0.0.1
options edns0 trust-ad
search xxxxxx.ts.net xxxxxxxxxx.local.net
      • soratoyuki@piefed.zipOPEnglish
        1·
        1 day ago

        So I was doing this from the (emulated?) terminal on my Android phone, and dig just returned command not found. I just got off work and moved to my desktop running Fedora, and on my desktop MagicDNS addresses work. Which I guess narrows things down.

        On my desktop, dig returns

         ; <<>> DiG 9.18.51-dev <<>> toshokun  
 # ;; global options: +cmd  
 ;; Got answer:  
 ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6364  
 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1  
 
 ;; OPT PSEUDOSECTION:  
 ; EDNS: version: 0, flags:; udp: 65494  
 ;; QUESTION SECTION:  
 ;toshokun.                      IN      A  
 
 ;; Query time: 3960 msec  
 ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)  
 ;; WHEN: Sat Nov 14 15:46:41 EST 2026  
 ;; MSG SIZE  rcvd: 37

        My resolv.conf is pretty similar. The namesever I’m pretty sure is correct for systemd reasons.

         nameserver 127.0.0.53  
 options edns0 trust-ad  
 search tail######.ts.net

        I appreciate the help, but realistically the answer to “Is that as simple a process as I want it to be?” is no, not quite, at least at my knowledge level lol. I’ll do more documentation reading in the meantime.

        • FedX@quokk.auEnglish
          1·
          1 day ago

          Interesting. Does trying to simply ping myhost or myhost.xxx.ts.net work?

          • soratoyuki@piefed.zipOPEnglish
            1·
            1 day ago

            On Android (well, GrapheneOS) both return temporary failure in name resolution.

            Pinging the Tailscale IP (the 100. one) returns 100% packet loss even though opening 100.whatever:#### works in a browser.

            • FedX@quokk.auEnglish
              1·
              1 day ago

              Ok, I think I am beginning to understand the issue. Can you try resolving the domain in your browser? If it’s a Firefox derivative, you can go to about:networking, and it gives you the ability to resolve a domain in the browser. Some Chrome based ones should have similar features, but YMMV.