Project

General

Profile

Actions
Copy link

Bug #15708

open

The filterdns service won't start

Added by Danilo Zrenjanin 3 months ago. Updated 22 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Aliases / Tables
Target version:
Future
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

If the filterdns.conf file contains more than 749 entries, the filterdns service will fail to start. This limitation applies regardless of whether the entries come from a single or multiple aliases.

When an alias includes both a hostname and IPs/subnets, the hostnames and IP entries are added to the filterdns.conf file. The ability to define a scope of IPs when specifying the host type Alias makes it relatively easy to trigger this behavior.

Here is an example of how to recreate this issue:

1. Define an Alias type Host(s), defining:
www.google.com
192.168.0.0-192.168.2.236
Save/Apply Changes

2. Navigate to the Diagnostics/Command Prompt and execute:

cat /var/etc/filterdns.conf | wc -l

You'll notice that there are 750 entries. (should be only one)

3. From the Diagnostics/Command Prompt, execute:

ps axww | grep filterdns

You'll notice that the filterdns service is not running.

4. Now navigate to the Alias defined in the first step and remove one entry (e.g 192.168.0.0).
Save and Apply the changes.

5. Repeat the step 2)
you'll notice that there are 749 entries

6. Repeat the step 3)
you'll notice that the filterdns service is running.

Actions
Copy link

Also available in: Atom PDF