Project

General

Profile

Actions

Bug #439

closed

TinyDNS: dnscache fails if LAN has no address assigned

Added by Henrik Kaare Poulsen over 15 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/21/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.0
Affected Plus Version:
Affected Architecture:

Description

BETA snapshot 20100321-0116

If you create a bridge for several LAN interfaces, you assign the bridge an address, but leave the LAN interface unassigned.
In TinyDNS, if you then enable DNS forwarding from LAN, DNS resolving does not work at all.

The problem seems to be in the function "tinydns_custom_php_changeip_command" in the file "tinydns.inc".

First the function sets

$ip = $config['interfaces']['lan']['ipaddr'];
[...]
$dnscacheip = $ip;

It then goes through great pains to get a $dnsserverip

However, after setting up tinydns:

exec("/usr/local/bin/dnscache-conf Gdnscache Gdnslog /etc/dnscache {$dnscacheip}");

But at this time, $dnscacheip is null.

In addition to the above, the "/etc/resolv.conf" written is invalid.

Proposal:

Have a radio-group or checkbox-group showing interfaces with (static) assigned addresses, and allow dnscache to be bound on one/any of those.

Actions

Also available in: Atom PDF