• 1 Post
  • 11 Comments
Joined 6 months ago
cake
Cake day: May 18th, 2026

help-circle

  • 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.


  • 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.