Specific ip address can not bypass pihole

Hello
i installed pihole and working perfectly.
i want to bypass pihole by one ip address

i added 04-bypass.conf in /etc/dnsmasq.d
dhcp-host=(8C:5D:36:C1:7D:B4,set:googlesdns1
But the bypass doesnt work

i added 04-bypass.conf in /etc/dnsmasq.d
dhcp-option=tag:googlesdns1,option:dns-server,8.8.8.8
dhcp-host=8C:5D:36:C1:7D:B4,set:googlesdns1,Hostname
But the bypass doesnt work again.

pihole -d

*** [ INITIALIZING ]
[i] 2019-07-15:19:59:34 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.1-0-g1a741f6

*** [ DIAGNOSING ]: Web version
[i] Web: v4.3 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3-0-g44aff72

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.3.1

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.45

*** [ DIAGNOSING ]: php version
[i] 7.2.19

*** [ DIAGNOSING ]: Operating system
[✓] Ubuntu 18.04.2 LTS

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[i] x86_64
*** [ DIAGNOSING ]: Ports in use
[::1]:631 cupsd (IPv6)
127.0.0.1:631 cupsd (IPv4)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
*:3127 squid (IPv6)
*:3128 squid (IPv6)
*:10000 miniserv.p (IPv4)
*:10000 miniserv.p (IPv6)
[*:53] is in use by pihole-FTL
[*:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.seevolution.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve www.seevolution.com via Pi-hole (192.168.1.180)
[✓] doubleclick.com is 172.217.169.142 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=single
    DNS_FQDN_REQUIRED=true
    DNS_BOGUS_PRIV=true
    DNSSEC=false
    CONDITIONAL_FORWARDING=false
    PIHOLE_INTERFACE=eth0
    IPV4_ADDRESS=192.168.1.180/24
    IPV6_ADDRESS=
    PIHOLE_DNS_1=4.2.2.4#53
    PIHOLE_DNS_2=
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    DHCP_ACTIVE=true
    DHCP_START=192.168.4.201
    DHCP_END=192.168.4.251
    DHCP_ROUTER=192.168.1.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=lan
    DHCP_IPv6=false
    DHCP_rapid_commit=false

*** [ DIAGNOSING ]: Dashboard and block page
[✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements.
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2680249 Tem 15 18:34 /etc/pihole/gravity.list
   -----head of gravity.list------
   0.0.0.0
   0.nextyourcontent.com
   0.r.msn.com
   0.start.bz

   -----tail of gravity.list------
   zzz.clickbank.net
   zzzezeroe.fr
   zzzpooeaz-france.com
   zzzrtrcm2.com
*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 381 Haz  7 16:46 /etc/pihole/adlists.list
   https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
   https://mirror1.malwaredomains.com/files/justdomains
   http://sysctl.org/cameleon/hosts
   https://zeustracker.abuse.ch/blocklist.php?download=domainblocklist
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
   https://hosts-file.net/ad_servers.txt

-rw-r--r-- 1 root root 0 Tem 15 19:59 /etc/pihole/blacklist.txt

-rw-r--r-- 1 root root 46 Tem 15 18:34 /etc/pihole/local.list
   192.168.1.180 kadikoyfw
   192.168.1.180 pi.hole

-rw-r--r-- 1 root root 238 Tem 15 18:33 /etc/pihole/logrotate
   /var/log/pihole.log {
        su root syslog
        daily
        copytruncate
        rotate 5
        compress
        delaycompress
        notifempty
        nomail
   }
   /var/log/pihole-FTL.log {
        su root syslog
        weekly
        copytruncate
        rotate 3
        compress
        delaycompress
        notifempty
        nomail
   }

-rw-r--r-- 1 root root 4 Tem 15 08:49 /etc/pihole/whitelist.txt
   --l
-rw-r--r-- 1 root root 1528 Tem 15 18:49 /etc/dnsmasq.d/01-pihole.conf
   addn-hosts=/etc/pihole/gravity.list
   addn-hosts=/etc/pihole/black.list
   addn-hosts=/etc/pihole/local.list
   localise-queries
   no-resolv
   cache-size=10000
   log-queries
   log-facility=/var/log/pihole.log
   local-ttl=2
   log-async
   server=4.2.2.4
   domain-needed
   bogus-priv
   interface=eth0

-rw-r--r-- 1 root root 485 Tem 15 19:08 /etc/dnsmasq.d/02-pihole-dhcp.conf
   dhcp-authoritative
   dhcp-range=192.168.4.201,192.168.4.251,24h
   dhcp-option=option:router,192.168.4.180
   dhcp-leasefile=/etc/pihole/dhcp.leases
   domain=lan

*** [ DIAGNOSING ]: contents of /etc/lighttpd

-rw-r--r-- 1 root root 3498 Tem 15 18:33 /etc/lighttpd/lighttpd.conf
   server.modules = (
        "mod_access",
        "mod_accesslog",
        "mod_auth",
        "mod_expire",
        "mod_compress",
        "mod_redirect",
        "mod_setenv",
        "mod_rewrite"
   )
   server.document-root        = "/var/www/html"
   server.error-handler-404    = "pihole/index.php"
   server.upload-dirs          = ( "/var/cache/lighttpd/uploads" )
   server.errorlog             = "/var/log/lighttpd/error.log"
   server.pid-file             = "/var/run/lighttpd.pid"
*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 361806 Tem 15 19:59 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2019-07-15 00:59:45.741 6849] Resizing "/FTL-queries" from 458752 to 688128
   [2019-07-15 06:53:25.674 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:25.674 6849] Blocking status is enabled
   [2019-07-15 06:53:25.675 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.1 msec (0 errors)
   [2019-07-15 06:53:25.716 6849] /etc/pihole/black.list: parsed 7 domains (took 0.0 ms)
   [2019-07-15 06:53:25.880 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 164.1 ms)
   [2019-07-15 06:53:26.010 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:26.010 6849] Blocking status is enabled
   [2019-07-15 06:53:26.010 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.1 msec (0 errors)
   [2019-07-15 06:53:26.049 6849] /etc/pihole/black.list: parsed 5 domains (took 0.0 ms)
   [2019-07-15 06:53:26.213 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 164.5 ms)
   [2019-07-15 06:53:26.377 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:26.377 6849] Blocking status is enabled
   [2019-07-15 06:53:26.377 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.2 msec (0 errors)
   [2019-07-15 06:53:26.418 6849] /etc/pihole/black.list: parsed 4 domains (took 0.0 ms)
   [2019-07-15 06:53:26.582 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 164.1 ms)
   [2019-07-15 06:53:26.805 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:26.805 6849] Blocking status is enabled
   [2019-07-15 06:53:26.806 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.2 msec (0 errors)
   [2019-07-15 06:53:26.850 6849] /etc/pihole/black.list: parsed 3 domains (took 0.0 ms)
   [2019-07-15 06:53:27.014 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 164.7 ms)
   [2019-07-15 06:53:32.167 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:32.167 6849] Blocking status is enabled
   [2019-07-15 06:53:32.168 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.2 msec (0 errors)
   [2019-07-15 06:53:32.211 6849] /etc/pihole/black.list: parsed 2 domains (took 0.0 ms)
   [2019-07-15 06:53:32.376 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 165.3 ms)
   [2019-07-15 06:53:38.111 6849] Received SIGHUP, reloading cache
   [2019-07-15 06:53:38.111 6849] Blocking status is enabled
   [2019-07-15 06:53:38.111 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.2 msec (0 errors)
   [2019-07-15 06:53:38.154 6849] /etc/pihole/black.list: parsed 3 domains (took 0.0 ms)
   [2019-07-15 06:53:38.320 6849] /etc/pihole/gravity.list: parsed 114597 domains (took 165.5 ms)
   [2019-07-15 07:05:57.549 6849] Received SIGHUP, reloading cache
   [2019-07-15 07:05:57.549 6849] Blocking status is enabled
   [2019-07-15 07:05:57.549 6849] Compiled 3 Regex filters and 1 whitelisted domains in 0.1 msec (0 errors)
   [2019-07-15 07:05:57.590 6849] /etc/pihole/black.list: parsed 2 domains (took 0.0 ms)

   -----tail of pihole-FTL.log------
   [2019-07-15 19:59:28.703 5561]    PORTFILE: Using /var/run/pihole-FTL.port
   [2019-07-15 19:59:28.703 5561]    SOCKETFILE: Using /var/run/pihole/FTL.sock
   [2019-07-15 19:59:28.703 5561]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
   [2019-07-15 19:59:28.703 5561]    BLACKLISTFILE: Using /etc/pihole/black.list
   [2019-07-15 19:59:28.703 5561]    GRAVITYFILE: Using /etc/pihole/gravity.list
   [2019-07-15 19:59:28.703 5561]    REGEXLISTFILE: Using /etc/pihole/regex.list
   [2019-07-15 19:59:28.703 5561]    SETUPVARSFILE: Using /etc/pihole/setupVars.conf
   [2019-07-15 19:59:28.703 5561]    AUDITLISTFILE: Using /etc/pihole/auditlog.list
*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 331776 Tem 15 19:59 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 108 Tem 15 19:59 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 98304 Tem 15 19:59 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 20480 Tem 15 19:59 /dev/shm/FTL-forwarded
-rw------- 1 pihole pihole 48 Tem 15 19:59 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 12288 Tem 15 19:59 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 458752 Tem 15 19:59 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Tem 15 19:59 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 8192 Tem 15 19:59 /dev/shm/FTL-strings
-rw------- 1 proxy proxy 8 Tem 15 19:03 /dev/shm/squid-cf__metadata.shm
-rw------- 1 proxy proxy 8216 Tem 15 19:03 /dev/shm/squid-cf__queues.shm
-rw------- 1 proxy proxy 44 Tem 15 19:03 /dev/shm/squid-cf__readers.shm

*** [ DIAGNOSING ]: Locale
    LANG=en_US.UTF-8

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 73833873 Tem 15 19:59 /var/log/pihole.log
   -----head of pihole.log------
   Jul 15 00:00:02 dnsmasq[6849]: query[A] spclient.wg.spotify.com from 192.168.4.51
   Jul 15 00:00:02 dnsmasq[6849]: forwarded spclient.wg.spotify.com to 4.2.2.6
   Jul 15 00:00:02 dnsmasq[6849]: reply spclient.wg.spotify.com is <CNAME>
   Jul 15 00:00:02 dnsmasq[6849]: reply wg.spotify.com is 35.186.224.53
   Jul 15 00:00:40 dnsmasq[6849]: query[A] v10.events.data.microsoft.com from 192.168.4.51
   Jul 15 00:00:40 dnsmasq[6849]: /etc/pihole/gravity.list v10.events.data.microsoft.com is 0.0.0.0
   Jul 15 00:03:01 dnsmasq[6849]: query[A] i2.hurimg.com from 192.168.4.51
   Jul 15 00:03:01 dnsmasq[6849]: cached i2.hurimg.com is <CNAME>
   Jul 15 00:03:01 dnsmasq[6849]: forwarded i2.hurimg.com to 4.2.2.6
   Jul 15 00:03:01 dnsmasq[6849]: query[A] www.hurriyet.com.tr from 192.168.4.51
   Jul 15 00:03:01 dnsmasq[6849]: cached www.hurriyet.com.tr is <CNAME>
   Jul 15 00:03:01 dnsmasq[6849]: forwarded www.hurriyet.com.tr to 4.2.2.6
   Jul 15 00:03:01 dnsmasq[6849]: query[A] s.hurriyet.com.tr from 192.168.4.51
   Jul 15 00:03:01 dnsmasq[6849]: cached s.hurriyet.com.tr is <CNAME>
   Jul 15 00:03:01 dnsmasq[6849]: forwarded s.hurriyet.com.tr to 4.2.2.6
   Jul 15 00:03:01 dnsmasq[6849]: reply i2.hurimg.com is <CNAME>
   Jul 15 00:03:01 dnsmasq[6849]: reply mr.tr.cubecdn.net is 195.201.167.178
   Jul 15 00:03:01 dnsmasq[6849]: reply mr.tr.cubecdn.net is 195.244.32.55
   Jul 15 00:03:01 dnsmasq[6849]: reply mr.tr.cubecdn.net is 95.216.45.108


root@xxx:/etc/pihole# dnsmasq --test
dnsmasq: syntax check OK.


Another question:is dhcp server without installing,spesific ip address can bypass pihole ?


Can you help me for two questions?
Thank you very much

Use dhcp-host=8C:5D:36:C1:7D:B4,set:googlesdns1,ipadress

More info here dnsmasq tags and conditional dns server - Stack Overflow

Tntdruid thank you.
But the problem is not solved.
My 04-baypass.conf is;

## The contents here bypass pihole by mac address
## This will go straight to Googles DNS Servers.
dhcp-option=tag:googlesdns1,6,8.8.8.8
dhcp-option=tag:googlesdns2,6,8.8.4.4

## This will go straight to Opendns Servers.
dhcp-option=tag:opendns1,6,208.67.222.220
dhcp-option=tag:opendns2,6,208.67.222.222
## OpenDNS FamilyShield
dhcp-option=tag:opendns3,6,208.67.222.123
dhcp-option=tag:opendns4,6,208.67.220.123

## Level3 DNS
dhcp-option=tag:Level3DNS1,6,4.2.2.1
dhcp-option=tag:Level3DNS2,6,4.2.2.2

## Comodo Secure DNS
dhcp-option=tag:ComodoSecureDNS,6,8.26.56.26
dhcp-option=tag:ComodoSecureDNS,6,8.20.247.20

## Norton
## P1 - malware, phishing schemes, and scams.
dhcp-option=tag:norton1,6,199.85.126.10
dhcp-option=tag:norton2,6,199.85.127.10
## P2 - Pornography
dhcp-option=tag:norton3,6,199.85.126.20
dhcp-option=tag:norton4,6,199.85.127.20
## P3 - Security + Pornography + Other
dhcp-option=tag:norton5,6,199.85.126.30
dhcp-option=tag:norton6,6,199.85.127.30

########################################################################

## Instructions
## First set your tag, and dns server.
## dhcp-option=tag:YOURTAGHERE,6,IPADDRESSOFDNSSERVER
## You then simply need to replace MA:CA:DD:R:ES:SS
## I have set up the standard DNS servertags above.
## Below are examples of how to set a mac address to bypass pihole.

## Your Device that goes to Google DNS
#dhcp-host=MA:CA:DD:R:ES:SS,set:googlesdns1

## Your Device that goes to OpenDNS
#dhcp-host=MA:CA:DD:R:ES:SS,set:opendns1

## Your Device that goes to custom DNS Server
#dhcp-host=MA:CA:DD:R:ES:SS,set:YOURTAGHERE
dhcp-host=10:bf:48:75:10:40,set:googlesdns1,192.168.2.51

root@emirates:cat /etc/pihole/black.list
deneme.com.tr

When i ping deneme.com.tr from 192.168.2.51,pihole.log is

Jul 19 00:04:47 dnsmasq[13199]: query[A] deneme.com.tr from 192.168.2.51
Jul 19 00:04:47 dnsmasq[13199]: /etc/pihole/black.list deneme.com.tr is 0.0.0.0

i can not achive bypass my pihole server

Have you any idea ?
Thank you very much

Please help me

Note that you have to restart FTL after you modify files in /etc/dnsmasq.d to have it read in your new configuration.

Use

sudo service pihole-FTL restart

for this. If it still doesn't work, you may also want to add log-dhcp to your file, restart again, restart the 192.168.2.51 machine and post here the related lines in /var/log/pihole.log.

DL6ER thank you.
But the problem is not solved.

i downloaded 04-bypass.conf from
"https://raw.githubusercontent.com/deathbybandaid/piadvanced/master/piholetweaks/dnsmasqtweaks/04-bypass.conf"

root@dddd:/etc/dnsmasq.d# ls -l
total 8
-rw-r--r-- 1 root root 1552 Tem 23 17:11 01-pihole.conf
-rw-r--r-- 1 root root 1709 Tem 23 11:27 04-bypass.conf

My 01-pihole.conf

root@dddd:/etc/dnsmasq.d# more 01-pihole.conf | grep [1]
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=15000
log-dhcp
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=8.8.8.8
server=4.2.2.6#53
domain-needed
bogus-priv
interface=eth1

Firstly ,04-bypass.conf ;

dhcp-option=tag:googlesdns1,6,8.8.8.8
dhcp-option=tag:googlesdns2,6,8.8.4.4
dhcp-option=tag:opendns1,6,208.67.222.220
dhcp-option=tag:opendns2,6,208.67.222.222
dhcp-option=tag:opendns3,6,208.67.222.123
dhcp-option=tag:opendns4,6,208.67.220.123
dhcp-option=tag:Level3DNS1,6,4.2.2.1
dhcp-option=tag:Level3DNS2,6,4.2.2.2
dhcp-option=tag:ComodoSecureDNS,6,8.26.56.26
dhcp-option=tag:ComodoSecureDNS,6,8.20.247.20
dhcp-option=tag:norton1,6,199.85.126.10
dhcp-option=tag:norton2,6,199.85.127.10
dhcp-option=tag:norton3,6,199.85.126.20
dhcp-option=tag:norton4,6,199.85.127.20
dhcp-option=tag:norton5,6,199.85.126.30
dhcp-option=tag:norton6,6,199.85.127.30
dhcp-option=tag:abcd,6,195.175.39.39
dhcp-host=10:bf:48:75:10:40,set:abcd

root@dddd:/etc/dnsmasq.d# dnsmasq --test
dnsmasq: syntax check OK.

i restarted pihole ftl .And then when the client can ping deneme.com.tr,the pihole.log is;

Jul 23 23:33:12 dnsmasq[6952]: query[A] deneme.com.tr from 192.168.2.51
Jul 23 23:33:12 dnsmasq[6952]: /etc/pihole/black.list deneme.com.tr is 0.0.0.0

Unfortunately,the client can not bypass pihole.

And i edited again 04-bypass.conf.
04-bypass.conf is;

dhcp-option=tag:googlesdns1,6,8.8.8.8
dhcp-option=tag:googlesdns2,6,8.8.4.4
dhcp-option=tag:opendns1,6,208.67.222.220
dhcp-option=tag:opendns2,6,208.67.222.222
dhcp-option=tag:opendns3,6,208.67.222.123
dhcp-option=tag:opendns4,6,208.67.220.123
dhcp-option=tag:Level3DNS1,6,4.2.2.1
dhcp-option=tag:Level3DNS2,6,4.2.2.2
dhcp-option=tag:ComodoSecureDNS,6,8.26.56.26
dhcp-option=tag:ComodoSecureDNS,6,8.20.247.20
dhcp-option=tag:norton1,6,199.85.126.10
dhcp-option=tag:norton2,6,199.85.127.10
dhcp-option=tag:norton3,6,199.85.126.20
dhcp-option=tag:norton4,6,199.85.127.20
dhcp-option=tag:norton5,6,199.85.126.30
dhcp-option=tag:norton6,6,199.85.127.30
dhcp-host=10:bf:48:75:10:40,set:ComodoSecureDNS

root@dddd:/etc/dnsmasq.d# dnsmasq --test
dnsmasq: syntax check OK.

i restarted pihole ftl .And then when the client can ping deneme.com.tr,the pihole.log is;

Jul 23 23:40:38 dnsmasq[7258]: query[A] deneme.com.tr from 192.168.2.51
Jul 23 23:40:38 dnsmasq[7258]: /etc/pihole/black.list deneme.com.tr is 0.0.0.0

Spesific ip address can not bypass pihole.

I've looked everywhere on the internet,but i can not solved the problem

  • i dont want to manually set the DNS on devices

Please do not offer me this solution.People facing the problem,how is solved this problem ?

Can you help me .
Thank you very much


  1. ^# ↩︎

Are you releasing the lease on the client and asking for a new lease when you change this?

Danschaper thank you for your answer.
Yes. I entered "ipconfig /flushdns "at client computer

That's not enough. You need to completely release the current DHCP lease on the client. All the flush command does is flush the local cache.

We dont have dhcp server in our network.i did not dhcp server in pihole server. we are entering all users manual ip.
Because our local programs work according to each user's given ip address.

Because of this situation(no dhcp server),spesific ip adress can not bypass pihole?

No, you can not assign a client a DNS server via a DHCP lease if you do not actually have the client receive the DNS server via DHCP lease. That's why all of the options are prefixed with dhcp.

Danschaper thank you.
I am so sorry.i did not understand.
At this situation;If i was disable dhcp server on pihole,the client did not bypass dns query .
Is it true?

If not true , should you suggest to me?(All the flush command does is flush the local cache./Yes i did)

No, you can not bypass Pi-hole in the way you are trying. You need to give the client a different DNS server to use. This is most often done by assigning the client a DNS server using DHCP.

Since you are manually setting the IP address on the client, set the DNS server to a non-Pi-hole DNS server at that time.

Danschaper thank you very much.
I set the dns server ip to a non-Pi-hole DNS server to my boss :slight_smile:
Other choice, i set the dns server ip to pihole.and then i write a client host file for entering allow sites address :slight_smile:

Thank you very much again.

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