[Pi-Hole] Adding blocking lists failed because of DNS resolution

[guillaumedc]

In Pi-Hole, when I add new blocking lists and trigger «Update Gravity», it ends up on a error:

[✗] DNS resolution is currently unavailable
[✗] DNS resolution is not available

All the rest of the UI works correctly.

I used the default values of docker-compose.yml

dns:
  - 127.0.0.1
  - 10.2.0.200
[...]
environment:
  DNS1: 10.2.0.200
  DNS2: 10.2.0.200
[...]
networks:
  private_networks:
    ipv4_address: 10.2.0.100
  default:

Do you have an idea of where it could come from?

[froid-san]

Also having the same issue and also using the defaults. Should I allow something on ufw?

[danielSanchezQ]

plus 1 here. It seems to be that the docker machine cannot access internet.