Project

General

Profile

Actions

Bug #7335

closed

DNS Forwarder exposed internal DNS Information to the outside world

Added by Florian Asche over 8 years ago. Updated over 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Forwarder
Target version:
-
Start date:
03/01/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.3
Affected Architecture:
amd64

Description

Hello dear devops,

im running pfsense 2.3.3. Im using the DNS Forwarder.
In General Setup - DNS Server Settings i configured a DNS-Server that is accessable over the WAN Gateway.
It is a Pihole DNS-Server to filter the DNS Requests.
That Server has many DNS requests, that shouldnt be there. There are DNS-Requests for my internal domain somedomain.local.

I also found out, that there is a change in /var/etc/hosts.

The lookup for hostname without the domain (somedomain.local) is missing. Lookup now will only work, if you configure the search-domain on all your servers.

Actions #1

Updated by Jim Pingle over 8 years ago

  • Status changed from New to Not a Bug

Please post on the forum for discussion. This is a configuration issue, not a bug.

Actions #2

Updated by Florian Asche over 8 years ago

Hello Mr Pingle,

are you sure about that?

I didnt change the configuration, i just did a update from 2.3.2 to 2.3.3.

There is a checkbox at "Do not forward private reverse lookups"
There is a checkbox at "If this option is set, pfSense DNS Forwarder (dnsmasq) will not forward A or AAAA queries for plain names, without dots or domain parts, to upstream name servers. If the name is not known from /etc/hosts or DHCP then a "not found" answer is returned."

I also did a roleback to the old version, and the problem is gone.

Actions

Also available in: Atom PDF