this post was submitted on 17 Nov 2023
1 points (100.0% liked)

Self-Hosted Main

515 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
[email protected]
1
How to have a local domain for my local network only (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
1 comments fedilink hide all child comments
 

Just a heads-up, everything that I'm writing below could be completely wrong since it's my newbie guesses, so if you have a better idea on how to do this, I'll listen.

Hello, I've been searching for a while, but I couldn't figure it out by myself how to do this, I've come across a few posts, so I know that this is possible.
So far, I know that I would need to assign a custom DNS, so my machine actually solves the domain locally. This part is covered (I think) since I use a OpenWrt router in my setup with the main DNS being the router itself.
But now I need to figure it out how to bind my host IP (192.168.2.X) to a local domain (example.home or something like that), I do use PBR on my router to preroute stuff to my VPN Interface, but nothing else, I think it can of use somehow.

This post is intended for me to learn this stuff, since I have no idea how to this, and I'm only that on my local network for the sake of it. So if there's any misconceptions or something that makes no sense, my bad.
If any info is needed, I'll gladly provide, thanks.

P.S. After doing the DNS part, if anyone knows about doing a self-signed certificate for each domain, I would appreciate it.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

If you already have adgaurd set up with your custom A records, all you have to do is point your client's dns to the IP of your adgaurd instance. If your running this on your router, than put your router's IP address as your client's dns. Use nslookup to troubleshoot dns requests and local domain lookup. If you have an A record "test.mydomain", run "nslookup test.mydomain" and reply with the results if the lookup doesn't work. Additionally if you'd like test to resolve to test.mydomain, you would have to include the search domain "mydomain" in your dns configuration.