Re: No nxdomain answer
Harm van Tilborg <[email protected]>
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
Hi Sergey, I assume you're probably thinking that tinydns does the same thing as BIND does: acting as both an authoritive nameserver _and_ a caching nameserver at the same time. That's not what it does. tinydns is only an authoritive nameserver. You will need djbdns' dnscache to setup a caching nameserver. See [1]. -- Kind regards, Harm van Tilborg [1] http://cr.yp.to/djbdns/run-cache-x.html Sergey Shepelev wrote: > Hello. > > I set up a tinydns instance: > > $ tinydns-conf temoto temoto /home/temoto/tinydns 127.0.0.1 > $ cd ~/tinydns/root > $ ./add-host some.foo 1.2.3.4 > $ make > $ cd .. > $ sudo ./run > > (it works! Great) > > $ dnsq a some.foo 127.0.0.1 really gives an answer, which is great. > > BUT. > > For dnsq a foo.bar 127.0.0.1 i don't get any answer. I would expect > nxdomain or some other error. Nothing. Timeout (after too much time, > BTW). > > What do i do wrong?