# DNS wont resolve :(

**URL:** <https://discourse.pi-hole.net/t/dns-wont-resolve/31932>\
**Category:** Help\
**Created:** [May 11, 2020, 10:10am UTC](https://discourse.pi-hole.net/t/dns-wont-resolve/31932 "2020-05-11T10:10:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [May 12, 2020, 11:35am UTC](https://discourse.pi-hole.net/t/dns-wont-resolve/31932/6 "2020-05-12T11:35:45Z")

</div>

> [@RustedBuckett](#):
>
> `/etc/dnsmasq.d/01-pihole.conf interface=enp3s0`

Am a bit puzzled as from above, Pi-hole is configured to only answer DNS queries on the `enp3s0` interface.

> [@RustedBuckett](#):
>
> ```auto
> [root@localhost ~]# nslookup pi.hole $(hostname -I)
> Server: 192.168.122.1
> Address: 192.168.122.1#53
> 
> ** server can't find pi.hole: NXDOMAIN
> 
> ```

But from above, you seem to get an answer from the IP on the `virbr0` interface.  
The answer is not the correct one though:

```auto
pi@noads:~ $ nslookup pi.hole $(hostname -I)
Server: 10.0.0.2
Address: 10.0.0.2#53

Name: pi.hole
Address: 10.0.0.2

```

Am wondering now, do you have some other DNS resolver running on the side ?

`sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471[1-8] '`

`nslookup -class=chaos -type=txt version.bind 192.168.1.101`

`nslookup -class=chaos -type=txt version.bind 192.168.122.1`

And does below file contain the `pi.hole` name with proper IP ?

`cat /etc/pihole/local.list`

If you want Pi-hole to resolve DNS queries on both the `enp3s0` and the `virbr0` interface, you can change below Pi-hole setting:

 ![image](https://discourse.pi-hole.net/uploads/default/original/2X/e/eb18579dc61ce1589e89e30bb88807f674d28415.png)

Also for diagnosing, you could try flush the firewall/iptables rules temporally just to be sure its not dropping network packets:

> [@Admin page shows FTL Offline | Unable to start, cannot access dhcp.leases](https://discourse.pi-hole.net/t/admin-page-shows-ftl-offline-unable-to-start-cannot-access-dhcp-leases/14129/21):
>
> Below ones seems to do the trick: sudo iptables -F sudo iptables -X sudo iptables -t nat -F sudo iptables -t nat -X sudo iptables -t nat -L -n -v sudo iptables -t mangle -F sudo iptables -t mangle -X sudo iptables -P INPUT ACCEPT sudo iptables -P OUTPUT ACCEPT sudo iptables -P FORWARD ACCEPT Check afterwards with: pi@noads:~ $ sudo iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source …

---

_[View the full topic](https://discourse.pi-hole.net/t/dns-wont-resolve/31932)._