Name Resolution in Client Activity Dashboard

[Troy_McClure]

hi,

The Clients where displayed with there Hostnames before the Update, is this a Bug or something like my fault?

[RamSet]

Doesn't seem to be happening on my side.

What does the footer of the /admin/ page show for version ?

Are/Were you getting your hostnames for the /etc/hosts file ?

[Troy_McClure]

4.0

no, i use my Fritzbox as individual upstream DNS for resolving local Names, worked well until the update

[RamSet]

Did you enable and configure the conditional forwarding option under DNS ?

[Troy_McClure]

no, this seems to be new with 4.0, will give it a try

[Troy_McClure]

The Update has messed everything up, just havnt noticed it...

Now it is up&running and even this Problem is solved, with conditional forwarding activated at the end

Thanks !

if you speak German: thats the whole mess ...

Fast nur noch Queries von der FBox?

Hi, damit auch die Anfragen der User im Gastnetzwerk der FBox gefiltert werden dachte ich es sei eine gute Idee der FBox als übergeordneten DNS auch einfach den Pi-Hole zu verpassen... Die Clients im internen Netz bekommen direkt den Pihole als DNS über den DHCP der FBox. Jetzt sehe ich in der Admin-Console dass der Löwenanteil der Anfragen von der Box kommt, obwohl zur Zeit niemand im Gastnetzwerk ist und die Anfragen z.B. auch definitiv von meinem PC kommen... Ausserdem ist bei den Forward D…

[peasea]

I am getting this problem after I upgraded to 4.0 today.

I am not using DHCP from Pi-hole - and have set /etc/hosts on the RPi to the local network names and IPs that are known to the DHCP server. This works fine for name lookups. So there is no really local router than maps ip names to addresses.

I've reverted back to the previous version to see if there is a solution.

[peasea]

It turns out I was reporting a browser issue. If it happens to you - reload the admin page several times and it all begins to work. Probably a consequence of updates to the JavaScript.

Doh.