this post was submitted on 18 Nov 2023
2 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]
2
DNS headache on self hosted server 🤦🏻‍♂️ (alien.top)
submitted 11 months ago by [email protected] to c/[email protected]
3 comments fedilink hide all child comments
 

I’m using mikrotik as my main router with ip 10.0.10.254

And I got a new desktop and turned it into proxmox server with ip 10.0.10.253

And installed adguard home to be my local dns server with ip of 10.0.10.250 and changed how it resolve hostnames by using 1.1.1.1 & 8.8.8.8

I also have another adguard server vm hosted on cloud with ip 190.190.190.200 for example

Configured mikrotik to use adguard as my primary dns server & cloud as secondary in (ip>dns)

But it only resolves hostnames when Allow remote requests is checked, when i uncheck it & remove my cloud dns vm it doesn’t resolve anything

Also in adguard quiery log the only client ip is my miktotik 10.0.10.254 it should be my local devices ip

What could be wrong?

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

This problem is presented in a confusing way. Pro tip: Spending the time to ask a well-organized question with all of the pertinent details sometimes gives you the answer before you ask. That said...

Okay, let's see if I have this right: You have a local network with a Mikrotik router as the gateway to the Internet, two Adguard DNS caching servers (one on the local network and one on the Internet), and a Proxmox server on the local network. The Adguard servers are pointed to 1.1.1.1 and 8.8.8.8, the DNS caching server in the Mikrotik router is pointed to the Adguard servers, and the Proxmox server is pointed to... what?

It sounds like—and this is just a guess—that the Proxmox server is getting its network configuration from the router via DHCP, which then points it at the router's internal DNS caching server. DNS queries go: Proxmox -> Mikrotik -> Adguard -> Google. When you turn off the router's DNS server (by unchecking "Allow remote requests"), the Proxmox server can't resolve any DNS queries for obvious reasons. (The DNS server it uses has been turned off!)

Everything works fine with the router's DNS caching server turned on, but if for some reason you want to turn it off, you need to point your local network devices (i.e. the Proxmox server) at a different DNS server. You usually do that by changing the DHCP settings on the router, so it sends DHCP clients the addresses of the Adguard DNS servers.