Explanation of dnsd.conf

[Denis Vlasenko]

On Thursday 05 October 2006 22:23, Roberto A. Foglietta wrote:
> Rory Vieira wrote:
> > Tito,
> > 
> > On 9/6/06, Tito <farmatito at tiscali.it> wrote:
> > 
> >>On Wednesday 6 September 2006 14:35, Rory Vieira wrote:
> >>
> >>>Hi list,
> >>>
> >>>Can someone please explain the contents of dnsd.conf?
> >>>I currently have
> >>>firewall 192.168.0.1
> >>>
> >>>resolv.conf
> >>>nameserver 127.0.0.1
> >>>
> >>>And from the machine, I do 'ping firewall', and it's perfect.
> >>>But 'ping test' also seems to work and resolves to 192.168.0.1 ?!?
> >>>Now where did that come from?
> >>
> >>Maybe /etc/hosts?
> > 
> > 
> > which contains:
> > 127.0.0.1 localhost
> > 
> > Side note:
> > I can ping ANYTHING <aka test or testing or whatever I type>
> > Everything is resolving back to the only ip in dnsd.conf
> > even if I ping the hostname of the machine itself it returns 192.168.0.1
> 
>   dnsd need this patch.
>   I did not receive any feed back about it
>   Please tell me if the patch was received or applied.

Please do not send mails to vda at ilport.com.ua, I do not work there anymore.

Patch is applied.

If you are a user of dnsd, can you help in testing?

Also, from the code I'd say that logging behavior of this thing
is haphazard: it writes to stderr even after daemonization,
isn't it going to mess up user's terminal? Shouldn't it just dup2()
fds 1 and 2 to logfile? And why it reopens logfile each time
it wants to write something?

Hm... oh no... IT DOES NOT open it because of this:

# grep daemonmode dnsd.c
static int daemonmode = 0;
        if (!daemonmode)

Yes, this is the complete optput of that grep! WTF??

IF you feel brave & want to fix that, here is the current svn version.
--
vda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dnsd.c
Type: text/x-csrc
Size: 10875 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20061006/6fe41d71/attachment-0002.c