Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Dec 2003 19:17:59 -0500
From:      "Greg Cirino - Cirelle Enterprises" <gcirino@cirelle.com>
To:        "::::Carlos:::Ariel:::Canta::::::::" <admin@redy.net.ar>
Cc:        freebsd-isp@freebsd.org
Subject:   Re: djbdns
Message-ID:  <004401c3c045$665f1690$fbb4a741@cedata.net>
References:  <oprz0sny1jg5bkrx@smtp.redynet.com.ar> <20031211151652.X61349@vette.gigo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
| > But my clients use de same ip for cache(dnscahe=3Dmy actully public =
ip) and

The basic logic for djbdns

tinydns - authorative IP
axfrdns - authorative IP

dnscache - alternate IP

tinydns used for resolving domains you own on UDP
axfrdns used for accepting requests from TCP (larger than 512)

dnscache used for resolving the internet (and your authorative domains)

Let's say your authorative domain server is registered with the internic =
as=20
NS.YOURDOMAIN.COM at IP 1.2.3.4 (this only contains domains you host)

tinydns should listen to 1.2.3.4
axfrdns should listen to 1.2.3.4

dnscache needs to be on a different IP (i.e. 1.2.3.5)

If you want your internal servers/workstations to be able to resolve the =
internet
you will need to change all primary dns entries in resolv.conf (or =
network on
windows machines) to the IP of dnscache (in this case 1.2.3.5).

A good reference can be found at:
http://lifewithdjbdns.org/

HTH
Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004401c3c045$665f1690$fbb4a741>