# Speedport W 724V

**URL:** <https://discourse.pi-hole.net/t/speedport-w-724v/17850>\
**Category:** Help\
**Created:** [February 28, 2019, 4:24pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850 "2019-02-28T16:24:27Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 4:24pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/1 "2019-02-28T16:24:27Z")

</div>

I've been trying repeatedly to setup Pi-hole network-wide, but I keep running into the same stuff. I watched people with the same Router that I own, did everything they did, just to find someone else's guide and start all over again. I've tried all 3 methods listed in this guide: [How do I configure my devices to use Pi-hole as their DNS server?](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245)

Router

- DHCP on
- local IPv6 address (ULA)
- Fixed DNS server address (primary DNS towards Pi, secondary towards 8 8 8 8 (Google))
- Sometimes I can't reach my Router's web page, it's random

Pi-hole

- doubles clients when I change the Router settings
- [http://pi.hole](http://pi.hole) is sometimes not available, it's random
- DHCP off
- Google (ECS)
- Doesn't block domains that I manually blacklist

I can't give you more details, for now, I'm too mad and frustrated. Just know that I disabled the adapter that pointed towards the Pi's IP, because that's apparently unnecessary. The video I watched from the guy with the same Router is this: [https://www.youtube.com/watch?v=rn1z-xBe720](https://www.youtube.com/watch?v=rn1z-xBe720)  
You will probably not understand him, because he speaks German. Nevertheless, I'm gonna vent and destroy something IRL

## Expected Behaviour:

_[Replace this text with what you think should be happening]_

## Actual Behaviour:

_[replace this text with what is actually happening]_

## Debug Token:

_[[https://tricorder.pi-hole.net/776w1v4ehd](https://tricorder.pi-hole.net/776w1v4ehd)]_

---

<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:** [February 28, 2019, 4:41pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/2 "2019-02-28T16:41:33Z")

</div>

Don't use primary/secondary DNS or a backup DNS. That's why things randomly work, sometimes you are using the Pi-hole and sometimes you are using Google.

> [@Why should Pi-hole be my only DNS server?](https://discourse.pi-hole.net/t/why-should-pi-hole-be-my-only-dns-server/3376):
>
> Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS serv…

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 4:43pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/3 "2019-02-28T16:43:30Z")

</div>

Do you see any reason why Pi-hole is not working in the logs? I just saw a problem with IPv6, but the problem persists, if I turn it off.

---

<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:** [February 28, 2019, 4:45pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/4 "2019-02-28T16:45:22Z")

</div>

The logs look fine. You're telling your clients to use Pi-hole and Google. They query for `pi.hole` and when it actually hits Pi-hole it works, when it goes to Google it doesn't. That's the randomness to the situation.

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 4:47pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/5 "2019-02-28T16:47:17Z")

</div>

Your debug log shows that Pi-Hole is working normally and is correctly processing all DNS queries it has received - in the last 24 hours this is the activity

```
   [2019-02-28 13:44:16.134 749] Imported 3632 queries from the long-term database
   [2019-02-28 13:44:16.134 749] -> Total DNS queries: 3632
   [2019-02-28 13:44:16.134 749] -> Cached DNS queries: 583
   [2019-02-28 13:44:16.134 749] -> Forwarded DNS queries: 2624
   [2019-02-28 13:44:16.134 749] -> Exactly blocked DNS queries: 411
   [2019-02-28 13:44:16.134 749] -> Unknown DNS queries: 14
   [2019-02-28 13:44:16.134 749] -> Unique domains: 424
   [2019-02-28 13:44:16.134 749] -> Unique clients: 3
   [2019-02-28 13:44:16.134 749] -> Known forward destinations: 4

```

As noted by @dschaper, your problem is not with Pi-Hole, but with the fact that some of your DNS requests are bypassing Pi-hole.

> [@Rob\_Dylan](#):
>
> Fixed DNS server address (primary DNS towards Pi, secondary towards 8 8 8 8 (Google))

Get rid of the 8.8.8.8 DNS in the router and all your DNS traffic will go through the Pi-Hole.

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 5:09pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/6 "2019-02-28T17:09:15Z")

</div>

Thank you for your help. I just had to point my adapter towards the Pi again, because I lost the connection, as soon as I made these changes to my router. According to Windows I still had internet access through, I just wasn't able to reach any website.  
This is a new log while being semi-offline:  
[https://tricorder.pi-hole.net/o1l1xebb76](https://tricorder.pi-hole.net/o1l1xebb76)

Now I'm connected again connected again through the adapter. I would like to turn that off though. Pi-hole works on my phone now I think

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 5:26pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/7 "2019-02-28T17:26:23Z")

</div>

Actually never mind. I thought Pi-hole worked on my phone, but I was able to access a page I blacklisted.

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 5:37pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/8 "2019-02-28T17:37:34Z")

</div>

> [@Rob\_Dylan](#):
>
> I disabled the adapter that pointed towards the Pi’s IP, because that’s apparently unnecessary.
> 
> Now I’m connected again connected again through the adapter

What adapter is this?

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 5:42pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/9 "2019-02-28T17:42:45Z")

</div>

![](https://discourse.pi-hole.net/uploads/default/original/2X/8/8cc1e18d9d7de132e718551894971d00796fafd5.png)  
That's the static Ip of the Pi

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 5:47pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/10 "2019-02-28T17:47:20Z")

</div>

That client is manually mapped to the Pi-Hole. What is the result if you check "Obtain the DNS server address automatically" and apply that setting? That will show the DNS that is being provided by the router during the DHCP handshake.

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 5:55pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/11 "2019-02-28T17:55:30Z")

</div>

That will unfortunately get me semi-offline again where I can't reach any website

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 6:37pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/12 "2019-02-28T18:37:07Z")

</div>

What is causing this? When you get the DNS automatically, what DNS are shown in the Windows box with` ipconfig/all`?

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 6:58pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/13 "2019-02-28T18:58:24Z")

</div>

I don't know. That's what keeps bugging me...  
[\>\>ipconfig/all](https://gist.github.com/robjane/4eae1f48f602fa47d3b6e071e997e4a8)

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 7:11pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/14 "2019-02-28T19:11:53Z")

</div>

Your router is passing itself and an IPv6 DNS to the client, and not the Pi-Hole DNS address. If you aren't using IPv6 on your network, I would disable that on the router and clients. That has frequently been a source of DNS bypass around Pi-Hole.

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 7:30pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/15 "2019-02-28T19:30:56Z")

</div>

Alright what I did is I used `pihole -r` to uncheck IPv6, then I went to my router settings and turned off IPv6 (ULA). Is that what you meant? Or do I need to do something else?

New debug log: [https://tricorder.pi-hole.net/tqtj1or5ye](https://tricorder.pi-hole.net/tqtj1or5ye)  
New Gist: [ipconfig/all](https://gist.github.com/robjane/445a5a26b919de3998e8b67ea334315d)

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 28, 2019, 7:46pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/16 "2019-02-28T19:46:31Z")

</div>

I think the problem lies in your router. Your Pi-Hole is working properly, and when clients send their DNS traffic to Pi-Hole it processes the traffic correctly.

I can't help you with your router since I don't have that model. I downloaded the manual and it doesn't seem to be very configurable. Until you sort the router out, if you manually assign your clients to use Pi-hole as DNS then you should have good results with your Pi-Hole.

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [February 28, 2019, 8:01pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/17 "2019-02-28T20:01:23Z")

</div>

![](https://discourse.pi-hole.net/uploads/default/original/3X/3/4/3484f888f038269ebaf6928a22813ba5ab710d00.png)  
 ![](https://discourse.pi-hole.net/uploads/default/original/3X/f/f/ff395d520ae6cf09e749736f5986189f2554eed4.png)

I'm not saying you're wrong, it's probably the router... and [@DL6ER](https://discourse.pi-hole.net/u/DL6ER) has the same [router](https://discourse.pi-hole.net/t/pi-hole-speedport-ipv6-ich-weiss-nicht-weiter/3585/2). I don't know how his setup works though. I appreciate the help 👍

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [February 28, 2019, 9:55pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/18 "2019-02-28T21:55:15Z")

</div>

> [@Rob\_Dylan](#):
>
> [@DL6ER](https://discourse.pi-hole.net/u/DL6ER) has the same [router](https://discourse.pi-hole.net/t/pi-hole-speedport-ipv6-ich-weiss-nicht-weiter/3585/2).

Small correction: DL6ER **had** the same router, I had to change the provider when I moved because Deutsche Telekom isn't offering stable Internet where I'm living now (rural area).

Long time ago, I cascaded a DD-WRT in between the Speedport and my network to be more flexible (and powerful) regarding firewall rules (like discard all DNS queries that do not come though the Pi-hole), so I might simply have missed the time when it didn't work anymore.

---

<div class="post-metadata">

**Author:** ![Rob\_Dylan](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@Rob\_Dylan](https://discourse.pi-hole.net/u/Rob_Dylan)\
**Post date:** [March 1, 2019, 12:17am UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/19 "2019-03-01T00:17:40Z")

</div>

What would you do in my situation? If there is no other workaround, I would consider buying a new router. The _Edgerouter X_ seems to be good, but I'm not sure whether or not my ISP (congstar) supports it. I might change my ISP anyway because I'm unsatisfied with my speeds. If I use Unitymedia for example, I'd have to use a TV cable 🤔

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [March 1, 2019, 4:54pm UTC](https://discourse.pi-hole.net/t/speedport-w-724v/17850/20 "2019-03-01T16:54:21Z")

</div>

> [@Rob\_Dylan](#):
>
> What would you do in my situation?

The same as I did: Put another router into the loop that is open for the modifications you want and not locked down to the bare minimum your ISP wants you to see.

I'm now living in Bavaria and here Vodafone (ex Kabel Deutschland) is providing the most reliable service over cable. I have the smallest package they offer (50 MBit/s) and am satisfied so far. I have a cable router without WiFi + my old DD-WRT router directly behind it. There is no reason to switch to cable TV if you're using DVB-T or -S.

[Next page](https://discourse.pi-hole.net/t/speedport-w-724v/17850.md?page=2)