# DNSCrypt not resolving some domains

**URL:** <https://discourse.pi-hole.net/t/dnscrypt-not-resolving-some-domains/1533>\
**Category:** Help\
**Created:** [January 30, 2017, 1:44pm UTC](https://discourse.pi-hole.net/t/dnscrypt-not-resolving-some-domains/1533 "2017-01-30T13:44:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Selaron](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/258eb7/32.png) [@Selaron](https://discourse.pi-hole.net/u/Selaron)\
**Post date:** [January 30, 2017, 1:44pm UTC](https://discourse.pi-hole.net/t/dnscrypt-not-resolving-some-domains/1533/1 "2017-01-30T13:44:06Z")

</div>

Hello,

after successfully setting up DNSCrypt on my pi-hole as decribed in github wiki: [https://github.com/pi-hole/pi-hole/wiki/DNSCrypt](https://github.com/pi-hole/pi-hole/wiki/DNSCrypt)  
I found some domain names unresolvable, e.g.:  
reply www.bountysource.com is NXDOMAIN  
using resolver cs-de.  
This domain resolves using resolver d0wn-de-ns1 but d0wn-de-ns1 dows not resolve e.g. www.postbank.de.

Is it a common issue that DNSCrypt resolvers do not resolve every domain?  
Can I tell dnsmasq or pi-hole to forward to a different resolver on NXDOMAIN responses?

All in all, the pi-hole works well with DNScrypt - except for some domains as mentioned above.

Kind regards

---

<div class="post-metadata">

**Author:** ![jpgpi250](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jpgpi250/32/286_2.png) [@jpgpi250](https://discourse.pi-hole.net/u/jpgpi250)\
**Post date:** [January 30, 2017, 1:53pm UTC](https://discourse.pi-hole.net/t/dnscrypt-not-resolving-some-domains/1533/2 "2017-01-30T13:53:52Z")

</div>

Don't know whether it's related, but check out [this post](https://discourse.pi-hole.net/t/dnssec-cloudfare-websites/1518), regarding DNSSEC (if you are also running this)  
my log says:  
Jan 30 14:50:54 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:50:54 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.1  
Jan 30 14:50:55 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:50:55 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:50:55 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.1  
Jan 30 14:50:56 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:50:56 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:50:56 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.1  
Jan 30 14:50:58 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:50:58 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:50:58 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.1  
Jan 30 14:51:02 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:51:02 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:51:02 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.1  
Jan 30 14:51:02 dnsmasq[620]: validation www.postbank.dE is **BOGUS**  
Jan 30 14:51:02 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:51:02 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:51:02 dnsmasq[620]: validation www.postbank.dE is **BOGUS**  
Jan 30 14:51:08 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:51:08 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:51:08 dnsmasq[620]: validation www.postbank.dE is **BOGUS**  
Jan 30 14:51:08 dnsmasq[620]: query[A] www.postbank.de from 192.168.2.125  
Jan 30 14:51:08 dnsmasq[620]: forwarded www.postbank.de to 127.10.10.2  
Jan 30 14:51:08 dnsmasq[620]: validation www.postbank.dE is **BOGUS**

I'm already running the correct dnsmasq version, so there appears to be something wrong with this domain.