Hi,
First you need to understand the "big picture":
Dnscache will run on your server (.132) and listen on your network
interface; this address will be known to your clients as the "dns server
ip".
Then you have tinydns running on the same server, but on lo0 and
listening to 127.0.0.1. It will only be contacted by dnscache, never by
a client from the network.
Dnscache then needs to be configured to ask 127.0.0.1 whenever a request
for your private domain comes in; all other things will be resolved
through the internet (root/servers/@ file).
*)
You should use a valid DNS name, even if it's for internal use; ".test"
is recommended for this.
e.g. straz.test
*)
# echo "172.16.144.129" > /etc/dnscache/root/servers/straz
should be
# echo "127.0.0.1" > /etc/dnscache/root/servers/straz
# echo "172.16.144.129" >
/etc/dnscache/root/servers/172.16.144.129.in-addr.arpa
should be
# echo "127.0.0.1" > /etc/dnscache/root/servers/144.16.172.in-addr.arpa
Wikipedia:
Reverse DNS lookups for IPv4 addresses use a reverse IN-ADDR entry in
the special domain in-addr.arpa. In this domain, an IPv4 address is
represented as a sequence of bytes in reverse order, encoded as decimal
numbers and separated by dots (full stop) with the second level domain
suffix .in-addr.arpa.
For example, an address (A) record for mail.example.com points to the IP
address 192.0.2.5. In pointer records of the reverse database, this IP
address is stored as the domain name 5.2.0.192.in-addr.arpa pointing
back to its designated host name mail.example.com. This allows it to
pass the Forward Confirmed reverse DNS process.
*)
# ./add-ns straz 172.16.144.132
should be
# ./add-ns straz 127.0.0.1
(I hope this is all correct, haven't done this in a while...)
kind regards,
Robert
Jan wrote:
Hello,
this is my first post on this list. I'm using OpenBSD for some weeks
now. I read around thousand pages about OpenBSD in the last months and
I'm happy to continue doing so. Unfortunately I've problems going on:
I'd like to run a local djbdns server that creates a TLD inside my LAN.
1)
I've installed daemontools, UCSPI-TCP and djbdns, using the guide from
djbdnsrocks.org.
2)
To configure djbdns I used the examples from
(www.mn-linux.org/meetings/pastnotes/djbdns.pdf):
# dnscache-conf dnscache dnslog /etc/dnscache 172.16.144.132give back
# ln -s /etc/dnscache /service/
# touch /etc/dnscache/root/ip/172.16.144
# echo "172.16.144.129" > /etc/dnscache/root/servers/straz
# echo "172.16.144.129" >
/etc/dnscache/root/servers/172.16.144.129.in-addr.arpa
//==> 172.16.144.129 is a Linux Box running apache
# tinydns-conf tinydns dnslog /etc/tinydns 127.0.0.1
# ln -s /etc/tinydns /service/
# cd /etc/tinydns/root
# ./add-ns straz 172.16.144.132
# ./add-host candle.straz 172.16.144.129
# make
This solution doesn't work. The 'dig' command runs out of time. When I
use the configuration describen on djbdnsrocks.org I'm able to use
djbdns as dns-server. But when I want to add my own namespace, it
doesn't work.
In the last week, I tried several solutions, but nothing worked out for
me. I would be happy if you can give me one or two buzzwords, about how
to go on.
Thanks!
Jan
