Project

General

Profile

Actions
Copy link

Bug #1768

closed

DNS Forwarder of Tinydns

Added by Oliver Loch over 12 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
08/13/2011
Due date:
% Done:

0%

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

Description

Hello,

just playing around with the TinyDNS package on pfs and found some "issues":

As far as I got it, the idea is to connect (create a socket) the TinyDNS Server to a loopback device (lo) and then use port forwarding to connect the "outer world" to the Server. That's fine.

The Forwarder will be listening on the interfaces one selects in the config page. If the LAN interface is selected, the tinydns server and forwarder come up - both listening on the configured devices, but the access to the forwarder is still denied.

I was wondering why and checkt /var/etc/dnscache${index}/root/ip and the only entry there is "127.0.0.1". Using this entry for the DNS Server seems ok, but for the forwarder?

I manually added my local subnet and the forwarder responded to my requests but was not delivering any data, so I searched on...

When enabling the TinyDNS Server, it adds itself as primary nameserver to /etc/resolv.conf. So all queries of the forwarder go to the server that only answers requests for it's SOA domain. Removing 127.0.0.1 from /var/etc/resolv.conf and restarting tinydns and the forwarder solved that problem.

Is this the expected behaviour or is there a bug in all of this? Or is the idea to assign the forwarder to another loopback interface and then use port forwarding for this as well?

I assume it's a bug and would like to patch the code to make it work again. If so, please just tell me :)

KR,

Oliver (Grimeton)

Files

tinydns.inc.diff (2.21 KB) tinydns.inc.diff Joshua Weage, 03/09/2012 02:06 PM
Actions
Copy link

Also available in: Atom PDF