DNS server is not running - dnsmasq

Hello, I I tried to put Pihole on my RP3 with latest Raspbain Stretch Lite, but during the installation I get an error:

[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary...
[✓] Downloading and Installing FTL
[i] FTL can now resolve DNS Queries without dnsmasq running separately
[✓] Stopping dnsmasq service...
[✓] Disabling dnsmasq service

[✓] man pages installed and database updated
[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
[✗] DNS resolution is currently unavailable
[i] Time until retry: 118^C

[i] User-abort detected
[✓] Cleaning up stray matter
[✗] DNS service is NOT running

Why did you abort the gravity run what is happening at that point is while FTLDNS is starting there is a status check running in the background that when it see's DNS resolution is available it will run Gravity and pull in blocked domains.

please run pihole -r and select repair and allow it to complete and if it still doesnt work please reprt back herew and I can give you some steps to try

If u about aborting 120 seconds, he will right that dns is not available (something like that, dont remember), I tried to repair it many times, I also tried to reinstall system

Please try the following steps

  1. sudo nano /etc/resolv.conf
  2. edit 127.0.0.1 to 9.9.9.9
  3. save
  4. Re-run pihole -r

I think something is borked in your install and this should resolve it

I did it early, but use 8.8.8.8

please run pihole -d for a debug token and share the token here

Token - 15ir52z0fm
Tried to repair with 9.9.9.9, at the end he wrote: dns resolution is currently unavailable

You need to allow the repair to finish ALL installations unless they are on blazing fast hardware will say that then within 30 seconds they will get name resolution back and continue and finish the install. this is an expected behaviour

Try this:

  1. sudo nano /etc/resolv.conf
  2. edit 127.0.0.1 to 9.9.9.9
  3. save
  4. sudo resolvconf -u
  5. test dns e.g. ping www.google.com

if you can ping google successful then continue with

  1. sudo pihole -r

I wait 180 seconds and he wrote same thing

Alright taking a look at your debug now hold tight will respond when i have more for you

Are you running anything alongside the Pi-hole i see FTLDNS binding to 5353 rather than port 53 which is what is causing your issues.

I changed in dnsmasq conf to 5353, cause pihole-Ftl service dont wanna start with 53 in dnsmasq config

Change it back to 53 save the file and run the repair again.

if it still isnt working please run another debug for me

Ok, now in web page I see that FTL offline, but repair was succesful
Token - qqbulgaslp

Update (for that I change port in dnsmasq):
root@Pi:~# service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sat 2018-08-25 01:50:50 +07; 5min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/pihole-FTL.service

Aug 25 01:50:49 Pi pihole-FTL[1377]: Stopped
Aug 25 01:50:49 Pi systemd[1]: Stopped LSB: pihole-FTL daemon.
Aug 25 01:50:49 Pi systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 25 01:50:49 Pi pihole-FTL[1424]: Not running
Aug 25 01:50:49 Pi pihole-FTL[1424]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or dire
Aug 25 01:50:50 Pi su[1476]: Successful su for pihole by root
Aug 25 01:50:50 Pi su[1476]: + ??? root:pihole
Aug 25 01:50:50 Pi su[1476]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 25 01:50:50 Pi pihole-FTL[1424]: dnsmasq: failed to create listening socket for port 53: Address alre
Aug 25 01:50:50 Pi systemd[1]: Started LSB: pihole-FTL daemon.

please try
sudo systemctl disable dnsmasq
then
sudo service dnsmasq stop
then
sudo service pihole-FTL start

1 Like

Thank you very match, now It's working

Glad to hear it! If you have anything else come up let us know.

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