Project

General

Profile

Bug #4332

Unable to run DNS Forwarder (dnsmasq) and DNS Resolver (unbound) simultaneously on different ports

Added by Jim Pingle almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
Start date:
01/28/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.2
Affected Architecture:

Description

It should be possible to run both services for different purposes so long as they are on different port numbers.

Currently the input validation on the DNS Resolver checks if the DNS Forwarder is enabled and won't allow both to be enabled ( source:usr/local/www/services_unbound.php#L112 ). Removing that input validation allows them both to run. The input validation should be changed so that it checks if they are attempting to use the same port number while both are enabled, and only reject that one case when they would conflict.

The same validation should be placed on the DNS Forwarder as well to avoid a port conflict if both are enabled, currently the DNS Forwarder does not check against the resolver.

Associated revisions

Revision 06e847a7 (diff)
Added by Chris Buechler almost 5 years ago

Check if Unbound is enabled and using the same port before allowing dnsmasq to be enabled. part of Ticket #4332

Revision 24cbfd5a (diff)
Added by Chris Buechler almost 5 years ago

Check if Unbound is enabled and using the same port before allowing dnsmasq to be enabled. part of Ticket #4332

Revision 0fe628a6 (diff)
Added by Chris Buechler almost 5 years ago

allow enabling Unbound when dnsmasq is enabled, if they're using diff
ports. Ticket #4332

Revision 8106d446 (diff)
Added by Chris Buechler almost 5 years ago

allow enabling Unbound when dnsmasq is enabled, if they're using diff
ports. Ticket #4332

History

#1 Updated by Chris Buechler almost 5 years ago

  • Status changed from Confirmed to Resolved

fixed

Also available in: Atom PDF