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
jfb
August 26, 2021, 10:04pm
2
What file is this? What is the output of the following from the Pi terminal?
sudo grep -v '#\|^$' -R /etc/dnsmasq.*
This is new intended behavior now, it was added here:
pi-hole:release/v5.4
← pi-hole:tweak/conditional_forwarding_unqualified_domains
opened 01:16PM - 20 Aug 21 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have r… ead and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template.
- [X] I have made only one major change in my proposed changes.
- [X] I have commented my proposed changes within the code.
- [X] I have tested my proposed changes, and have included unit tests where possible.
- [X] I am willing to help maintain this change if there are issues with it later.
- [X] I give this submission freely and claim no ownership.
- [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
- [X] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
---
**What does this PR aim to accomplish?:**
Ensure conditional forwarding will forward unqualified host names if we have no local answer for them.
**How does this PR accomplish the above?:**
Add `server=//a.b.c.d` config option.
`man dnsmasq`:
> An empty domain specification, `//` has the special meaning of "unqualified names only" ie names without any dots in them.
Conditional forwarding can unleash its full power only when these two check boxes are unticked, but this should be fairly clear from the hint below them (highlighted in the screenshot):
![Screenshot from 2021-08-20 15-14-23](https://user-images.githubusercontent.com/16748619/130238894-6f0edf9a-ca5c-472a-b7ae-a7c13a15724f.png)
**What documentation changes (if any) are needed to support this PR?:**
None
1 Like
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.
Do you have Never Forward non-FQDNs
checked or unchecked in Settings?
Yes, that tells FTL to forward unqualified names (hostnames without domains) to the rev-server for conditional forwarding.
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.
DL6ER
August 27, 2021, 2:54pm
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 runpihole restartdns
?
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.