[prev in list] [next in list] [prev in thread] [next in thread] 

List:       djbdns
Subject:    Re: dnsip works but dig and host get dropped for inval arg
From:       prj () case ! edu (Paul Jarc)
Date:       2019-02-06 7:48:35
Message-ID: ozkd8sytgxws.fsf () webapps-d-2 ! tis ! cwru ! edu
[Download RAW message or body]

Bob Dodds <bobdodds@yandex.com> wrote:
> Also yes it is important to use the right query tool as far as one
> that will allow specifying which nameserver (address) to use.  The
> ones that do not take an ip, fail silently, and that was what dnsip
> was doing

You're correct that those tools ignore extra arguments, and don't
inform you that you made a mistake in your invocation.  But that
doesn't mean they can't do what you want--you just have to express
what you want in the way these tools are designed to accept, instead
of the way you're used to from host and dig.  If you read the djbdns
documentation (or reread Bruce's last message), you'll see that you
have to do it differently for most of these tools.

> Asking about IPSEND is good, and then too what is said in the ./run file can
> contradict and fail on that same sort of detail.

IPSEND affects only dnscache, not the command line query tools.  So
its value in your shell doesn't matter--only the value used in the run
script.

> /etc/sv/dnscache/env/IPSEND
> 127.0.0.53

That looks like a mistake.  You won't be able to send queries from a
127.* address to any other machine.  Try using 0.0.0.0 here instead.
[prev in list] [next in list] [prev in thread] [next in thread]