Please advise / additional dnsmasq entries

General
1

I was reading this, I wonder if it is recommended to add these dnsmasq configuration entries.

Thanks for the advice.

2

They are referring to a custom OpenWRT config file called rfc6761.conf:

# RFC6761 included configuration file for dnsmasq
#
# includes a list of domains that should not be forwarded to Internet name servers
# to reduce burden on them, asking questions that they won't know the answer to.

server=/bind/
server=/invalid/
server=/local/
server=/localhost/
server=/onion/
server=/test/

Pinging @moderators for their opinion about this.

The RFC says this about localhost:

Caching DNS servers SHOULD recognize localhost names as special
 and SHOULD NOT attempt to look up NS records for them, or 
 otherwise query authoritative DNS servers in an attempt to
 resolve localhost names.

Similarly for the others.

The RFC also says the same for the following domains:

     10.in-addr.arpa.      21.172.in-addr.arpa.  26.172.in-addr.arpa.
     16.172.in-addr.arpa.  22.172.in-addr.arpa.  27.172.in-addr.arpa.
     17.172.in-addr.arpa.  30.172.in-addr.arpa.  28.172.in-addr.arpa.
     18.172.in-addr.arpa.  23.172.in-addr.arpa.  29.172.in-addr.arpa.
     19.172.in-addr.arpa.  24.172.in-addr.arpa.  31.172.in-addr.arpa.
     20.172.in-addr.arpa.  25.172.in-addr.arpa.  168.192.in-addr.arpa.

which are not included in the OpenWRT config file.

Pi-hole already implements this (and even including IPv6 private ranges) via the web interface option "Never forward reverse lookups for private IP ranges".

Side note: OpenWRT also includes dhcpbogushostname.conf but we already have this in 01-pihole.conf. There are no other default OpenWRT config files.

7
10

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.