this post was submitted on 14 Nov 2026
60 points (96.9% liked)

Selfhosted

63843 readers
254 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] FedX@quokk.au 2 points 1 day ago (1 children)

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.zip 1 points 1 day ago (1 children)

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 1 points 1 day ago (1 children)

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

[–] soratoyuki@piefed.zip 1 points 1 day ago (1 children)

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.au 1 points 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.