Pi-Hole won't resolve DNS requests

I tried PIHOLE DHCP service once. Didn't get it to work. No IP has been assigned.

Can you tell me what I need to set to get PHOLE DHCP to run?

What is the output of:

cat /etc/pihole/pihole-FTL.conf

Let's fix the first problem first.

SOCKET_LISTENING=all
QUERY_DISPLAY=yes
AAAA_QUERY_ANALYSIS=yes
RESOLVE_IPV6=no
RESOLVE_IPV4=yes
MAXDBDAYS=365
DBINTERVAL=1.0
DBFILE=/etc/pihole/pihole-FTL.db
MAXLOGAGE=24
FTLPORT=4711
PRIVACYLEVEL=0
IGNORE_LOCALHOST=no
BLOCKINGMODE=IP-NODATA-AAAA
REGEX_DEBUGMODE=false

And the output of the following please:

cat /etc/pihole/setupVars.conf

WEBPASSWORD=hidden
DHCP_ACTIVE=false
DHCP_START=192.168.178.20
DHCP_END=192.168.178.23
DHCP_ROUTER=192.168.178.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=local
DHCP_IPv6=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.178.22/24
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
API_EXCLUDE_DOMAINS=
API_EXCLUDE_CLIENTS=127.0.0.1
API_QUERY_LOG_SHOW=all
API_PRIVACY_MODE=false
TEMPERATUREUNIT=C
WEBUIBOXEDLAYOUT=boxed
DNSMASQ_LISTENING=single
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=true
CONDITIONAL_FORWARDING_IP=192.168.178.1
CONDITIONAL_FORWARDING_DOMAIN=fritz.box
CONDITIONAL_FORWARDING_REVERSE=178.168.192.in-addr.arpa

my hosts-file, maybee wrong settings?
127.0.0.1 localhost
127.0.1.1 DietPi

127.0.0.1 pi.hole
192.168.178.22 DietPi
192.168.178.22 pi.hole

maybee it will help...

nslookup pi-hole.net
Server: 9.9.9.9
Address: 9.9.9.9#53

Non-authoritative answer:
Name: pi-hole.net
Address: 206.189.252.21

root@DietPi:~# nslookup pi-hole.net
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find pi-hole.net: REFUSED

oh, my mistake, 192.168.178.22 is correct.

what is the full output of the following commands from the terminal on the Pi-Hole platform?

dig bloomberg.com - this is a site that is typically not blocked in a block list

dig flurry.com - this site is on many block lists

dig bloomberg.com

; <<>> DiG 9.10.3-P4-Debian <<>> bloomberg.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14596
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;bloomberg.com. IN A

;; ANSWER SECTION:
bloomberg.com. 600 IN A 69.191.252.148
bloomberg.com. 600 IN A 69.187.23.20

;; Query time: 19 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Thu Aug 09 07:17:22 BST 2018
;; MSG SIZE rcvd: 74

dig flurry.com

; <<>> DiG 9.10.3-P4-Debian <<>> flurry.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20115
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;flurry.com. IN A

;; ANSWER SECTION:
flurry.com. 300 IN A 212.82.100.153
flurry.com. 300 IN A 98.136.103.26
flurry.com. 300 IN A 74.6.136.153

;; Query time: 32 msec
;; SERVER: 9.9.9.9#53(9.9.9.9)
;; WHEN: Thu Aug 09 07:17:50 BST 2018
;; MSG SIZE rcvd: 87

i typed it in Mate-Terminal. Where is Pihole Terminal?

Pi-Hole doesn't have a terminal. I was referring to whatever command line terminal you had on the Pi-Hole host platform.

Did you run pihole -r ? If not, please run this, select reconfigure and report results.

  [i] Existing PHP installation detected : PHP version 7.0.30-0+deb9u1
  [i] Reconfigure option selected
  [✓] Disk space check

  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... up to date!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Using interface: eth0
  [i] Using DNS.WATCH servers
  [i] Static IP already configured
  [i] Unable to find IPv6 ULA/GUA address, IPv6 adblocking will not be enabled
  [i] IPv4 address: 192.168.178.22/24
  [i] IPv6 address: 
  [i] Web Interface On
  [i] Web Server On
  [i] Logging On.
  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for psmisc
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [✓] Checking for sqlite3
  [✓] Checking for libcap2-bin
  [✓] Checking for dns-root-data
  [✓] Checking for resolvconf
  [✓] Checking for lighttpd
  [✓] Checking for php7.0-common
  [✓] Checking for php7.0-cgi
  [✓] Checking for php7.0-sqlite3

  [✓] Enabling lighttpd service to start on reboot
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [✓] No dnsmasq.conf found... restoring default dnsmasq.conf...
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✗] Backing up index.lighttpd.html
        No default index.lighttpd.html file found... not backing up

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected x86_64 architecture
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v4.0). Confirming Checksum...
  [i] Checksum correct. No need to download!


  [✓] Installing new IPTables firewall rulesets
  [i] man not installed
  [i] Systemd-resolved is not enabled
  [✓] Starting lighttpd service
  [✓] Enabling lighttpd service to start on reboot
  [i] Restarting services...
  [✓] Starting pihole-FTL service
  [✓] Enabling pihole-FTL service to start on reboot
  [✓] Deleting existing list cache
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 157595
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 134366
  [i] Number of whitelisted domains: 0
  [i] Number of blacklisted domains: 110
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
  [i] View the web interface at http://pi.hole/admin or http://192.168.178.22/admin

tested: with 127.0.0.1 in resolv.conf = not working DNS-name-resolution

with 9.9.9.9 = yes

What did this test consist of? A DNS lookup from a client, a DNS lookup from the Pi-Hole platform terminal?

What does your similar admin page screen look like?

Has this installation of Pi-Hole ever worked for you? Or, did it fail after an update or after changing a parameter or router settings?

New Reconfigure (Install) worked with no errors but
I still can't visit websites if 127. 0. 0. 1 is set in resolv. conf. Then my Internet won't work anymore.