It looks like the router settings are correct for DNS.
I'll defer to others with more expertise on dnscryp-proxy for the settings. I don't use that and don't want to steer you wrong.
Have you tried using Google DNS for the PiHole to make sure the PiHole is working correctly? Once you do that, you can change to DNS of your choice later.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] disk-of56.stream is 38.133.143.13 via localhost (127.0.0.1)
[✓] disk-of56.stream is 38.133.143.13 via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)
now, resolve via pihole works but:
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 does not match the IP found in /etc/pihole/setupVars.conf
When I put 192.168.178.21/24 in SetupVars.conf then Pihole resolv won't work but
the error "ip does not match" disappeared.
What can I do?
Must I put pihole ip to my "hosts"-file?
192.168.178.21 pi.hole
0.0.0.0 pi.hole
What is correct?
local.list: (pihole)
0.0.0.0 amd
0.0.0.0 pi.hole
PIHOLE_INTERFACE=enp4s0
IPV4_ADDRESS=0.0.0.0
IPV6_ADDRESS=
PIHOLE_DNS_1=84.200.69.80
PIHOLE_DNS_2=84.200.70.40
QUERY_LOGGING=false
INSTALL_WEB=false
LIGHTTPD_ENABLED=0
Is this setting correct in NetworkManager?
Status of pihole-FTL:
Router_Ports:
Blocking ads won't work.
Blocking websites won't work.
Some idea?
Output:
Server: 127.0.0.1
Address: 127.0.0.1#53
This is mandatory to be set to the Pi-hole IP 192.168.178.21/24 in order for your router to communicate with the DNS server based on:
PIHOLE_DNS_1= needs to be your Unbound resolver
You have all the settings tangled and messed up.
You might want to start from scratch and reference DNSCrypt How-to guide?
Maybe you will find some related information.
I personally use only Pi-hole+Unbound and no DNScrypt
...and how I can set an unbound-ip to my localhost?
##########################
include: "/etc/unbound/unbound.conf.d/*.conf"
server: 192.168.178.22 ???
hide-identity: yes
hide-version: yes
use-caps-for-id: yes
module-config: "iterator"
val-permissive-mode: yes
domain-insecure: "example"
do-not-query-localhost: no
interface: enp4s0 ???
access-control: 0.0.0.0/0 allow
port: 533
do-ip4: yes
do-ip6: no
do-udp: yes
do-tcp: yes
forward-zone:
name: "."
forward-addr: 127.0.0.1@5333 (to dnsmasq)
forward-first: no
remote-control:
control-enable: no
correct?
ok, I'll tried out the pi-hole unbound guide, all set in pihole.conf @ /etc/unbound/unbound.conf.d
Unbound starts, no errors in Terminal but when I type:
dig pi-hole.net @127.0.0.1 -p 5353
Output:
DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> pi-hole.net @127.0.0.1 -p 5353
;; global options: +cmd
;; connection timed out; no servers could be reached
some Idea?
which unbound address must I put in pihole setupVars.conf?
PIHOLE_DNS_1=
Which address to use?
private-address: 192.168.0.0/16
private-address: 172.16.0.0/12
private-address: 10.0.0.0/8
my network local ip is 192. 168. 178. 21, how do i have to change unbound's address?
If you set up per the instructions, PiHole uses 127.0.0.1#5353 to get its DNS lookups from unbound.
...with this config, dig pi-hole.net @127.0.0.1 works now.
Output:
DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> pi-hole.net @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41846
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1252
;; QUESTION SECTION:
;pi-hole.net. IN A
;; ANSWER SECTION:
pi-hole.net. 83326 IN A 206.189.252.21
;; Query time: 159 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jul 13 03:41:30 CEST 2018
;; MSG SIZE rcvd: 67
server:
##//Specify the INTERFACE-address to listen on:
interface: 127.0.0.1
##//LISTEN on all INTERFACEZ:
#interface: 0.0.0.0
hide-identity: yes
hide-version: yes
use-caps-for-id: yes
module-config: "iterator"
val-permissive-mode: yes
domain-insecure: "example"
do-not-query-localhost: no
access-control: 0.0.0.0/0 allow
port: 533
do-ip4: yes
do-ip6: no
do-udp: yes
do-tcp: yes
forward-zone:
name: "."
##//FORWARD to "dnsmasq"//
forward-addr: 127.0.0.1@5333
forward-first: no
remote-control:
control-enable: no
forward-addr: 127.0.0.1@5353 to pihole? correct?
in /etc/unbound/unbound.conf.d/01-pihole-conf: which port to use? port: 5353 or port: 5333 (dnsmasq)
I type:
nslookup www.google.cz 127.0.0.1 = (works) got answer 
dig pi-hole.net @127.0.0.1 @5333 = (works) got answer
dig pi-hole.net @127.0.0.1 @5353 = (works) got answer
in
/etc/dnsmasq.d/01-pihole.conf
##//DNSCRYPT-PROXY//##
server=127.0.2.1#513
server=127.0.2.2#513 correct?
/etc/pihole/SetupVars.conf (pihole)
PIHOLE_DNS_1=server=127.0.0.1#5353 correct?
When I set in PIHOLE SetupVars.conf = IPV4_ADDRESS=0.0.0.0:
all green, no errors:
Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] h2i.it is 62.149.128.154
62.149.128.151
62.149.128.157
62.149.128.160 via localhost (127.0.0.1)
[✓] h2i.it is 62.149.128.154
62.149.128.157
62.149.128.160
62.149.128.151 via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)
When I set in PIHOLE SetupVars.conf = IPV4_ADDRESS=192.168.178.21/24:
The error "192.168.178.21/24 does not match the IP found in /etc/pihole/setupVars.conf" is not gone...
Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] jacobxx.co.uk is via localhost (127.0.0.1)
[✗] Failed to resolve jacobxx.co.uk via Pi-hole (192.168.178.21)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)
with 0.0.0.0,
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ads139.hpg.com.br is 187.31.64.20 via localhost (127.0.0.1)
[✓] ads139.hpg.com.br is 187.31.64.20 via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✗] lighttpd daemon is inactive
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
API_EXCLUDE_DOMAINS=
API_EXCLUDE_CLIENTS=
API_QUERY_LOG_SHOW=all
API_PRIVACY_MODE=true
PIHOLE_INTERFACE=enp4s0
IPV4_ADDRESS=0.0.0.0
#IPV4_ADDRESS=192.168.178.21/24
IPV6_ADDRESS=
QUERY_LOGGING=false
INSTALL_WEB=false
LIGHTTPD_ENABLED=1
#DNSMASQ_LISTENING=single
##//UPSTREAM_DNS_SERVER//##
PIHOLE_DNS_1=server=127.0.0.1#5353
#PIHOLE_DNS_1=server=127.0.2.1#513
#PIHOLE_DNS_2=server=127.0.2.2#513
#PIHOLE_DNS_1=84.200.69.80
#PIHOLE_DNS_2=84.200.70.40
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSSEC=true
#CONDITIONAL_FORWARDING=false
can I ignore 192.168.178.21/24 does not match the IP found in /etc/pihole/setupVars.conf???
Or how can I fix it?
with the new configs, my PIHOLE blocks nothing, no ads What I've made wrong... damn....
token: jysgrzc0kb
I'm a little bit further:
sudo lighty-enable-mod fastcgi
service lighttpd force-reload
sudo lighty-enable-mod fastcgi-php
service lighttpd force-reload
now I can get into the pi-hole admin dashboard but can't save any settings in dashboard
When I set in SetupVars.con IPV4_ADDRESS=192.168.178.21/24
pihole -d says:
Failed to resolve www.pbsi.stkippersada.ac.id via Pi-hole (192.168.178.21)
IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 does not match the IP found
When I set in SetupVars.conf IPV4_ADDRESS=0.0.0.0
all "green":
Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mg-multimedia-services.com is via localhost (127.0.0.1)
[✓] mg-multimedia-services.com is via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 172.217.19.78 via a remote, public DNS server (8.8.8.8)
and:
IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 does not match the IP found
In Pihole Dashboard:
Network Information
Pi-hole Ethernet Interface: unknown
Pi-hole IPv4 address: unknown
Pi-hole IPv6 address: unknown
Pi-hole hostname: flashgordon
I don't know why pihole is nothing to block.
What is the result of ip a ?
ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether c6:2e:d0:75:80:88 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.21/24 brd 192.168.178.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet 169.254.140.105/16 brd 169.254.255.255 scope global enp4s0
valid_lft forever preferred_lft forever
debug token is: 4nz4bp6dc2
hmm...
nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find pi.hole: NXDOMAIN
Netstat_Results:
Active Network Services
@anon62498003, correct me if I'm wrong here, but it appears like you're trying to accomplish a couple of things here:
0.0.0.0
53?)Might I be so bold as to suggest trying out the FTLDNS beta? You will be able to acheieve these things without the "hacky" workarounds that you are currently using!
echo "FTLDNS" | sudo tee /etc/pihole/ftlbranch
pihole checkout core FTLDNS
pihole checkout web FTLDNS
Once you're on that branch, you will be able to set BLOCKINGMODE=NULL in /etc/pihole/pihole-FTL.conf, which solves the first issue. You can also set ports on upstream servers. E.g, I have unbound running on my machine, listening on port 5353, which I simply tell Pi-hole about like this:
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
