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?

  • soratoyuki@piefed.zipOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days 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.

    • FedX@quokk.au
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 days 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.zipOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 days 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.au
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 days ago

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

          • soratoyuki@piefed.zipOP
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 days 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.