Actions
Bug #4332
closed
Unable to run DNS Forwarder (dnsmasq) and DNS Resolver (unbound) simultaneously on different ports
Start date:
01/28/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
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.
Updated by
Actions