Project

General

Profile

Bug #243

filterdns does not resolve hostnames with a network mask

Added by Seth Mos over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
Start date:
12/22/2009
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

On a network alias where a hostname is used with a subnetmask this will not correctly work for filterdns.

The alias contains 2 entries, 1st 127.0.0.1/32 as a dummy, 2nd is hostname/32.
Below is the output I gathered from the shell.

  1. more /var/etc/filterdns.conf
    hostname/32 = ext_management
  2. pfctl -t ext_management -T show
    127.0.0.1
  3. ps auxw |grep filterdns
    root 45003 0.0 0.7 4608 1664 ?? Is 10:46PM 0:00.01 /usr/local/sbin/filterdns /tmp/filterdns.pid 300 /var/etc/filterdns. #

History

#1 Updated by Seth Mos over 9 years ago

Added the extra parameter "3" for debugging to the filterdns startup in filter.inc.

Now it logs this:
  1. clog /var/log/system.log | grep -i filterdns
    Dec 22 22:52:33 lutjebroek filterdns: Found hostname leaf.dnsalias.org with netmask 32.
    Dec 22 22:52:33 lutjebroek filterdns: host_dns: could not parse "leaf.dnsalias.org": hostname nor servname provided, or not known
    Dec 22 22:52:33 lutjebroek filterdns: Found -1 entries for leaf.dnsalias.org
    Dec 22 22:52:33 lutjebroek filterdns: Not cleaning table ext_management host leaf.dnsalias.org.

Indeed DNS did not work because the system was missing a default route.

#2 Updated by Seth Mos over 9 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF