so i do sudo service dnsmasq stop and reboot. Then DNS is running correctly.
piboy@rasp:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[✓] Everything is up to date!
a new debug show :
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mkt354.com is 22.214.171.124 via localhost (127.0.0.1)
[✗] Failed to resolve mkt354.com via Pi-hole (192.168.0.40)
[✓] doubleclick.com is 126.96.36.199 via a remote, public DNS server (188.8.131.52)
*** [ DIAGNOSING ]: Pi-hole processes
[✗] dnsmasq daemon is inactive
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
Not sure if I am missing something....
You should not run dnsmasq anymore.
Latest Pihole-FTL has dnsmasq "build in" An update to latest version would have disabled DNSmasq for you during update
Disable dnsmasq during boot should fix your issue. As you start the old dnsmasq before the Pihole-ftl service, port 53 is in use.
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Wed 2018-09-26 21:16:07 CEST; 9min ago
sept. 26 21:16:07 rasp systemd: Starting LSB: pihole-FTL daemon...
sept. 26 21:16:07 rasp pihole-FTL: Not running
sept. 26 21:16:07 rasp pihole-FTL: Failed to set capabilities on file `/usr/bin/pihole-FTL' (Operation not supported)
sept. 26 21:16:07 rasp pihole-FTL: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
sept. 26 21:16:07 rasp su: Successful su for pihole by root
sept. 26 21:16:07 rasp su: + ??? root:pihole
sept. 26 21:16:07 rasp su: pam_unix(su:session): session opened for user pihole by (uid=0)
sept. 26 21:16:07 rasp pihole-FTL: dnsmasq: failed to create listening socket for port 53: Permission denied
sept. 26 21:16:07 rasp systemd: Started LSB: pihole-FTL daemon.