Confusion using dnsdist with pihole

Help understanding what dnsdist ip:port should I fill in pihole dns setting for DNS Upstream server

Added downstream server 192.168.0.15:8533
,No certificate provided for DoH endpoint 0.0.0.0:80, running in DNS over HTTP mode instead of DNS over HTTPS
,Listening on 0.0.0.0:8053
,Listening on 0.0.0.0:80 for DoH
,ACL allowing queries from: ::1/128, fc00::/7, 10.0.0.0/8, 169.254.0.0/16, 127.0.0.0/8, 172.16.0.0/12, 100.64.0.0/10, 192.168.0.0/16, fe80::/10
,Console ACL allowing connections from: 127.0.0.1/8, ::1/128
,Webserver launched on 0.0.0.0:8085
,Marking downstream Pi-hole (192.168.0.15:5335) as 'down'

This is the log of dnsdist running in docker, and my pihole is also running in docker but exposed via port 8533.

I added this line in dnsdist config
newServer({address="192.168.5.165:8533", name="Pi-hole", checkName="dc01.domain.nl.", checkInterval=60, mustResolve=true})

the confusion is while I was testing other dns servers I did not had to specify pihole ip:port inside of dns server.

but now in dnsdist I am trying to use DoH so I also specified :slightly_smiling_face:

addLocal('0.0.0.0:8053', { reusePort=true })
addDOHLocal("0.0.0.0", nil, nil, "/dns-query", { reusePort=true }) # I am yet to setup certs once I get this working.

so is it the since my docker is running on the same node 192.168.0.15 where I have exposed dnsdist port 8053, so should I fill in 192.168.0.15:8053 in the pihole upstream server ?

so is the listening server the upstream server ?

Listening on 0.0.0.0:8053
,Listening on 0.0.0.0:80 for DoH

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.