Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS resolution is currently unavailable #1800

Closed
ghost opened this issue Dec 7, 2017 · 12 comments

Comments

@ghost
Copy link

commented Dec 7, 2017

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

How familiar are you with the the source code relevant to this issue?:

1


Expected behaviour:

The pihole -g command would run and finish without errors.

Actual behaviour:

When running pihole -g I get the following message:

[✗] DNS resolution is currently unavailable
[i] Waiting up to 118 seconds before continuing

Steps to reproduce:

Just run pihole -g

Debug token provided by uploading pihole -d log:

rvbvhp661q

Troubleshooting undertaken, and/or other relevant information:

Tried a clean install with no success. Thanks with any help!!!

@dschaper

This comment has been minimized.

Copy link
Member

commented Dec 7, 2017

Thank you for the report, we are looking in to this.

@ookangzheng

This comment has been minimized.

Copy link

commented Dec 7, 2017

Me too. I've clean install on Ubuntu
Your debug token is: da7i0s6q5f

@dschaper

This comment has been minimized.

Copy link
Member

commented Dec 7, 2017

Thank you, I think we have narrowed down where this is happening and I have opened an issue to try and resolve it.

@dschaper

This comment has been minimized.

Copy link
Member

commented Dec 7, 2017

@RexBelli

This comment has been minimized.

Copy link

commented Dec 8, 2017

Just wanted to add my own experience. I got that error doing a pihole -up, however subsequent pihole -ups say all is good. No idea what's going on.

::: Checking for updates...
::: Pi-hole Core:   update available
::: FTL:            update available
::: Web Interface:  update available
:::
::: Updating Pi-hole core and web admin files
:::
::: Checking for existing repository...
:::    Updating repo in /etc/.pihole... done!
 done!

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.


  [✓] Root user check
  [i] Performing unattended setup, no whiptail dialogs will be displayed
  [✓] Disk space check

  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... 3 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [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] SELinux mode detected: Disabled
  [✓] Check for existing repository in /etc/.pihole
  [✓] Update repo in /etc/.pihole

  [✓] Check for existing repository in /var/www/html/admin
  [✓] Update repo in /var/www/html/admin

  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsmasq
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✗] Checking for idn2 (will be installed)
  [✓] Checking for lighttpd
  [✓] Checking for php-common
  [✓] Checking for php-cgi
  [✗] Checking for php-sqlite3 (will be installed)
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Creating log and changing owner to dnsmasq... log already exists!

  [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...
  [✓] Downloading and Installing FTL
  [i] Restarting services...

  [✓] Starting dnsmasq service

  [✓] Enabling dnsmasq service to start on reboot

  [✓] Starting lighttpd service

  [✓] Enabling lighttpd service to start on reboot

  [✓] Starting pihole-FTL service

  [✓] Enabling pihole-FTL service to start on reboot

  [i] Preparing to run gravity.sh to refresh hosts...
  [i] Cleaning up previous install (preserving whitelist/blacklist)
  [i] Running gravity.sh
  [✗] DNS resolution is currently unavailable
  [✗] DNS resolution is not available
Unable to complete update, contact Pi-hole
rex@r:~$ nslookup www.google.com
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   www.google.com
Address: 172.217.6.68

rex@r:~$ pihole -up
  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] FTL:              up to date
  [i] Web Interface:    up to date

  [✓] Everything is up to date!
@Happyfeet01

This comment has been minimized.

Copy link

commented Dec 11, 2017

Have the same issue. Is there any solution?

root@odroid64:~# pihole -g
  [✗] DNS resolution is currently unavailable
  [i] Waiting up to 119 seconds before continuing...^C

  [i] User-abort detected
  [✓] Cleaning up stray matter
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
root@odroid64:~# pihole -up
  [i] Checking for updates...
fatal: unable to access 'https://github.com/pi-hole/pi-hole.git/': Could not resolve host: github.com
  [i] Pi-hole Core:     up to date
  [i] FTL:              update available

  [i] FTL out of date

  [i] FTL Checks...
  [✓] Detected ARM-aarch64 architecture
  [i] Checking for existing FTL binary...
  [✗] Downloading and Installing FTL
  Error: Unable to get latest release location from GitHub
@viperdriver2000

This comment has been minimized.

Copy link

commented Dec 11, 2017

@Happyfeet01
whats in your /etc/resolf.conf ?
only nameserver 127.0.0.1 ?
change it to

nameserver 8.8.8.8
nameserver 8.8.4.4

then you can resolve github.com.

@dschaper dschaper added this to the v3.2.1 milestone Dec 12, 2017

@DiehrWolf

This comment has been minimized.

Copy link

commented Dec 16, 2017

I had the opposite resolution.
my /etc/resolf.conf already contained:
nameserver 8.8.8.8
nameserver 8.8.4.4

Everything started working once I changed it to:
nameserver 127.0.0.1

@dschaper

This comment has been minimized.

Copy link
Member

commented Dec 22, 2017

Closed via #1856

@dschaper dschaper closed this Dec 22, 2017

@Kiina

This comment has been minimized.

Copy link

commented Mar 25, 2018

Just in case anyone on arch has the same problem and finds this issue:

Edit your /etc/hosts with 127.0.0.1 pi.hole and it will work again

@poldim

This comment has been minimized.

Copy link

commented Apr 6, 2018

Just echoing that adding 127.0.0.1 pi.hole resolved this for me.

Since I'm in a docker, I had to:

apt-get update
apt-get install nano -y
nano etc/hosts

@dschaper - Any thoughts why this would still be required when running the latest docker image?

@max72bra

This comment has been minimized.

Copy link

commented Nov 28, 2018

Last comments are not fully correct. This is a generic Linux configuration issue that has nothing to do with Pi-hole. You should follow the wiki guides of your distributions to see what they recommend.

As a generic hint, assuming 'domain.local' as your domain name:

$ cat /etc/resolv.conf
# Generated by resolvconf
search domain.local
nameserver 127.0.0.1

Assuming 'mypi' as the local hostname:

$ cat /etc/hosts      
127.0.0.1           localhost.domain.local   localhost
::1                 localhost.domain.local   localhost

<lanip_v4>          mypi.domain.local     mypi
<lanip_v6>          mypi.domain.local     mypi

127.0.0.1 is localhost and should never be the hostname

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
10 participants
You can’t perform that action at this time.