>have Pihole set up
>want to have internal DNS for gitlab and other services
>decide upon technitium
>set technitium for upstream DNS on pihole
>it eats shit and dies whenever pihole queries it

can anyone suggest to me a dockerized dns that has good web UI and doesn't do bullshit like deny zone transfers out of nowhere?

What is the use case for running your own local DNS server (unless it's for ad blocking) if it's just going to query an external server to resolve requests anyway?

>>105864056
I have gitlab, jellyfin, transmission, email and openwebui on my self hosted server so I will probably do a reverse proxy and have few nice LAN urls

>>105864071
Just put it in your hosts file bruv

>>105864080
yea, but how does it resolve to a specific port?
Hosts file only does url to ip connection
reverse proxy sees what url you're querying and it just gives you a port as well

>>105864087
What in fuck are you talking about? That's handled transparently by the server on the reverse proxy. How does this relate to DNS in any way?

>>105864111
DNS can do ip allocation dynamically through rDNS and server would ping back to the DNS with the PTR record? It's just a more structured and robust solution tho, I know I can do it with static IP, and server is on the static IP but this feels more robust

thanks tho, I will most probably do it through hosts file until I get DNS working

>>105864149
I really just have no idea what you are yapping about, you seem to be confusing a nameserver and a reverse proxy

Nginx reverse proxy or whatever:
shit.balls --> port 6969 (jellyfin)
nigger.balls --> port 1234 (gitlab)
poop.balls --> port 8080 (transmission)
listen on 192.168.0.69 or whatever the server ip is

Hosts file:
shit.balls 192.168.0.69
nigger.balls 192.168.0.69
poop.balls 192.168.0.69

That's all you have to do

>>105864174
yea but if server IP changes you're fucked, so my idea is to have a reverse DNS application that would ping to the DNS server "hey, this is my current IP" every minute
This is done through PTR record on the zone, and you can do a zone on the *.machine.internal for example to divide up the servers to their IPs

>>105864087
A reverse proxy doesn't negotiate a connection through a specific port like you seem to think it does
The point is that it makes the connection itself and then proxies it through a single port (typically 80 or 443)
So if you connect to nigger.balls:80, the proxy will connect to localhost:1234 on your behalf and then end the result through port 80
>>105864209
It's honestly deranged that you would rather set up a whole nameserver with a dynamic dns script than just configure a static IP on your network

>>105864227
as I said, it's just more structured and robust solution

oh yeah that

>>105864041 (OP)
>pihole
>gitlab
>docker
kys OP

>>105864238
>it's just more structured and robust solution
No it's fucking not

what if dont care about ad blocking all my devices though

>>105864238
"Structured and robust solution" which involves moving parts (a whole DNS server which is an additional service you need to maintain and point local devices to, and a script running on your server every minute to update the IP address if it happens to change because of the DHCP server that you control anyway)
It also allows the server to be unavailable for up to a minute anytime the IP changes
Just configuring a static IP on your own network eliminates all of these problems and is the standard solution that any sane person would choose instead

>>105864247
so your server changes IP due to some change in the networking you're doing and then you have to go in the hosts file and change it line by line?
and you would rather do that, even if its once in a blue moon, than have an automated self correcting solution? I would understand if you called me solutionist but its obviously more robust and structured solution than a fucking hosts file

>>105864279
There is literally no situation where you allocate a static IP address on your network and it changes for no reason. That's a made up situation you invented.

>>105864299
>for no reason
I mentioned the reason, change in the networking?
What if I want to shift around subnet allocations? What if i want to change routers even? Add in a switch and you're shitting bricks all of the sudden? I don't have a datacenter in my house, but a man can have dreams no?

>>105864279
>implying the hacky nonstandard dns script held together with duct tape wouldn't break more often

>>105864314
"Change in the networking" is a meaninless phrase, what are you doing that is causing your subnet to change erratically?
If you changed routers you'd have to alter DNS settings again regardless, so why is that even a situation you need to be prepared for?
You're a faggot

>>105864334
>>105864318
stay in your hosts file lane, niggers

>>105864279
>>105864314
So what will you do to prevent your dns server's ip address from changing?
Warning: don't answer this question (the answer will probably cause you to have a meltdown)

>>105864365
>changing one line of IP somewhere in the DNS configs
compared to
>changing 10 lines of IPs in hosts file

use case?

>>105864378
>moving the goalpost this hard
This is the worst cope I've ever seen
>changing 10 lines of IPs in hosts file
It's the same IP address every line

>>105864314
Pihole has a centralized hosts file. I have static IPs for all my services and query domains from the list hosted in pihole. Best of both worlds.
If pihole goes down I can use direct IP to connect to my hypervisor. If your dns everything solution goes down you'll have to physically connect to your hypervisor or metal host for dns to fix it because you don't know the last IP it had.
Set static IPs for shit you're running 24/7. Keep your network organized for fucks sake.