Printing blank server for reverse server lookups inside dnsmasq.d config file

General beta
1

It appears as
rev-server=192.168.1.0/24,192.168.1.1
server=//192.168.1.1
server=/some.lan/192.168.1.1

when it only needs to be .....

rev-server=192.168.1.0/24,192.168.1.1
server=/some.lan/192.168.1.1

2

What file is this? What is the output of the following from the Pi terminal?

sudo grep -v '#\|^$' -R /etc/dnsmasq.*

3

This is new intended behavior now, it was added here:
https://github.com/pi-hole/pi-hole/pull/4287

1 Like
4

01-pihole.conf

it list
rev-server=192.168.1.0/24,192.168.1.1
server=//192.168.1.1
server=/some.lan/192.168.1.1
instead of
rev-server=192.168.1.0/24,192.168.1.1
server=/some.lan/192.168.1.1

is server=//192.168.1.1
actually doing something critical. if so, please explain. Some of these changes may be breaking to some configurations.

5

Do you have Never Forward non-FQDNs checked or unchecked in Settings?

6

Yes, that tells FTL to forward unqualified names (hostnames without domains) to the rev-server for conditional forwarding.

7

unchecked

8

I don't know why, but now I am experiencing issues resolving IPV6 names with this added. And I just updated yesterday, so this issue is new. Now all my ipv6 lookups are coming as refused. Before this addition they were accepted.

9

@SomeWhereOutThere I don't think this will be related to the recent change.

  • Can you try re-checking the box?
  • Why did you un-check it in the first place (there are good reasons to do this but what caused you doing it)?
  • Does the issue you observe vanish when you remove the line manually and run
    pihole restartdns
    ?
12

The Box is unchecked because I am not using Pihole for DHCP. I am using it only for DNS and conditional forwarding. I was under the impression this option should only be checked if the pihole user was issue DHCP via Pihole as oppose to via a Router DHCP assignment.