# Adguard + Unbuond Configuration ISSUE

**URL:** <https://dietpi.com/forum/t/adguard-unbuond-configuration-issue/15246>\
**Category:** Troubleshooting\
**Created:** [15 December 2022 00:14 UTC](https://dietpi.com/forum/t/adguard-unbuond-configuration-issue/15246 "2022-12-15T00:14:47Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [15 December 2022 09:29 UTC](https://dietpi.com/forum/t/adguard-unbuond-configuration-issue/15246/8 "2022-12-15T09:29:05Z")

</div>

ok as next step, let’s try to catch what unbound is doing while trying to resolve DNS request. I have the feeling, it’s going into direction of blocked DNSSEC request [Unbound not working with pi-hole](https://dietpi.com/forum/t/unbound-not-working-with-pi-hole/14431)

First, we need the `tcpdump` tool to be installed

```auto
apt install tcpdump

```

Stop AGH

```auto
systemctl stop adguardhome

```

Once done start `tcpdump` on 1st SSH session

```auto
tcpdump -i any -c500 -nn port 53 or port 5335

```

On a 2nd SSH session, perform a test

```auto
dig @127.0.0.1 -p 5335 google.com

```

Stop/cancel `tcpdump` and restart AGH

---

_[View the full topic](https://dietpi.com/forum/t/adguard-unbuond-configuration-issue/15246)._