# Upstream DNS (opendns) custom web filtering not working \[SOLVED - D-LINK ROUTER INCOMPATIBILITY\]

**URL:** <https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464>\
**Category:** Help\
**Created:** [November 2, 2016, 3:43pm UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464 "2016-11-02T15:43:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 2, 2016, 3:43pm UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/1 "2016-11-02T15:43:13Z")

</div>

Goal:  
I want my traffic to go to pihole -\> opendns (for web filtering) -\> web  
I don't want to use family shield (need proxy on occasion)  
.  
Issue:  
Web filtering stopped working when I moved to pihole  
OpenDNS ip update client says i'm not connected  
.  
Setup:  
router points to pi's IP  
pihole conf files confirmed to have openDNS IPs setup  
.  
Troubleshooting checks:  
with openDNS ip's in my router for dns - i have web filtering (but no pihole obviously)  
with pi IP for router DNS, I have NO web filtering

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [November 2, 2016, 3:44pm UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/2 "2016-11-02T15:44:41Z")

</div>

Can you run a `pihole -d` and get us the token value so we can start to take a look at things for you?

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 2, 2016, 9:46pm UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/4 "2016-11-02T21:46:48Z")

</div>

Hi -  
I ran pihole -d and attached the log- any help is appreciated!  
...can't attach a .txt file; so i'm trying a link to a google doc; I did not see a token in the terminal output, I don't think the upload worked.  
[log file](https://drive.google.com/open?id=0B8C8reT2J-_wUnhZQkhqZjV1UG8)  
.  
Edit; i've now realized why i got no "token" - the pi itself can't connect to the net - but otherdevcies can, and the admin page shows dns activity - so that's pretty confusing. I'm assuming pihole didn't install correctly if it killed the pi net access.

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 3, 2016, 5:20pm UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/5 "2016-11-03T17:20:13Z")

</div>

Yeah, it looks like your Pi-hole is blocking ads correctly, but it cannot reach the upstream servers. What's the output of

```auto
cat /etc/resolv.conf

```

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:31am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/6 "2016-11-04T03:31:47Z")

</div>

I was bothered that my install was old. I did a fresh raspian install; pihole install; then updated. lots of reboots. when i got pi-hole up and running again, i lost internet access on the pi again. that's a little bothersome - but i'm glad you guys are helping!  
.  
here are results for cat / etc/resolv.conf  
.  
Generated by resolvconf  
nameserver 127.0.0.1

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:37am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/7 "2016-11-04T03:37:40Z")

</div>

What about output from this command

```auto
ip route | grep default

```

and the first couple lines from

```auto
traceroute doubleclick.com
traceroute google.com

```

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:43am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/8 "2016-11-04T03:43:29Z")

</div>

pi@raspberrypi:~ $ ip route | grep default  
default via 192.168.2.1 dev eth0 metric 202  
.  
pi@raspberrypi:~ $ traceroute doubleclick.com  
traceroute to doubleclick.com (192.168.2.3), 30 hops max, 60 byte packets  
1 0000mps.webpreview.dsl.net (192.168.2.3) 0.117 ms 0.061 ms 0.049 ms  
.  
traceroute google.com ...  
pi@raspberrypi:~ $ traceroute google.com  
google.com: Name or service not known  
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:44am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/9 "2016-11-04T03:44:31Z")

</div>

```auto
ping 192.168.2.1

```

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:45am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/10 "2016-11-04T03:45:27Z")

</div>

pi@raspberrypi:~ $ ping 192.168.2.1  
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.  
From 192.168.2.3 icmp\_seq=1 Destination Host Unreachable  
From 192.168.2.3 icmp\_seq=2 Destination Host Unreachable  
From 192.168.2.3 icmp\_seq=3 Destination Host Unreachable  
From 192.168.2.3 icmp\_seq=4 Destination Host Unreachable

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:47am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/11 "2016-11-04T03:47:32Z")

</div>

```auto
arp -a | grep '(192.168.2.1)'

```

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:48am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/13 "2016-11-04T03:48:17Z")

</div>

pi@raspberrypi:~ $ arp -a | grep '(192.168.2.1)'  
? (192.168.2.1) at c4:a8:1d:8a:78:a4 [ether] on eth0

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:48am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/14 "2016-11-04T03:48:49Z")

</div>

How is your Pi connected to the network?

When you ping it, it seems to be responding with a different IP address...

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:49am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/15 "2016-11-04T03:49:26Z")

</div>

Since your Pi cannot access your router (gateway) you won't be able to get out to the Internet, thus no upstream servers can be contacted.

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:49am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/16 "2016-11-04T03:49:29Z")

</div>

pi has an ethernet cable running to 1 of 4 router ports

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:50am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/17 "2016-11-04T03:50:24Z")

</div>

yea; whats weird is everything was just fine (web access) but web fails when i install pihole (or perhaps when i set the dns on the router to point to pi)

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:52am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/18 "2016-11-04T03:52:51Z")

</div>

Send a screenshot of where you made this change in the router.

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:54am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/19 "2016-11-04T03:54:33Z")

</div>

attached.

 ![](https://discourse.pi-hole.net/uploads/default/original/3X/5/5/55e66a53f324356328f34cffcb6d921a5672ec1c.png)

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 3:56am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/20 "2016-11-04T03:56:22Z")

</div>

Stumped for now. I'll try again tomorrow

---

<div class="post-metadata">

**Author:** ![picante](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/43a26b/32.png) [@picante](https://discourse.pi-hole.net/u/picante)\
**Post date:** [November 4, 2016, 3:58am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/21 "2016-11-04T03:58:10Z")

</div>

is it in some kind of death loop - pi tries to get dns from router, but gets sent back to itself...? but i assume that's the whole point. Alright - I'll wait on you (because i have no clue!).  
If i uninstall pihole, and see if internet access returns, would that be of any help?

The problem is DEFINATELY turned on/off when I set the DNS to the pi on the router; when i set it to pi, pi loses WAN access; when it's not set it _can_ access the WAN.

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [November 4, 2016, 11:09am UTC](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464/22 "2016-11-04T11:09:52Z")

</div>

Can other devices on your network get out to the Internet?

Your D-Link router is responding to pings with your Pi's IP address for some reason.

[Next page](https://discourse.pi-hole.net/t/upstream-dns-opendns-custom-web-filtering-not-working-solved-d-link-router-incompatibility/464.md?page=2)