Project

General

Profile

Actions

Bug #3868

closed

Problem with DNSmasq resolution when using multiple DNS suffixes

Added by Eduard Rozenberg over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DNS Forwarder
Target version:
-
Start date:
09/17/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.x
Affected Architecture:
amd64

Description

Hello,

My pfSense DHCP server is configured to give out the following "Domain search list"
(names changed):

lan.city1.mycompany.net;mycompany.net;city2.mycompany.net

I'm running the pfSense DNS forwarder which responds to all DNS queries on the LAN.

If I ping a host on the "company.net" domain (a machine not on the local LAN),
using for example "ping server1" I get a strange response sometimes
(does not happen 100% of the time):

PING server1.lan.city1.mycompany.net (198.105.254.68): 56 data bytes

I get this also when doing the ping on the pfsense box itself.

This IP (198.105.254.68) is not configured anywhere on the
pfSense firewall so I have no idea where it comes from, and
why pfSense gives this as a DNS response. The proper response
would be record not found so that my LAN machines would
work their way through the DNS suffix list until they find
the correct match.

========

Version 2.1.5-RELEASE (amd64)
built on Wed Aug 27 15:14:26 EDT 2014
FreeBSD 8.3-RELEASE-p16

You are on the latest version.
Platform pfSense
CPU Type Intel(R) Atom(TM) CPU D525 @ 1.80GHz
4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads

Actions

Also available in: Atom PDF