Re: djbdns
From: Greg Cirino - Cirelle Enterprises (gcirino_at_cirelle.com)
Date: 12/12/03
- Previous message: Jason Fesler: "Re: djbdns"
- In reply to: Jason Fesler: "Re: djbdns"
- Next in thread: Wolfpaw - Dale Corse: "RE: djbdns"
- Reply: Wolfpaw - Dale Corse: "RE: djbdns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "::::Carlos:::Ariel:::Canta::::::::" <admin@redy.net.ar> Date: Thu, 11 Dec 2003 19:17:59 -0500
| > But my clients use de same ip for cache(dnscahe=my 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
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
_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
- Previous message: Jason Fesler: "Re: djbdns"
- In reply to: Jason Fesler: "Re: djbdns"
- Next in thread: Wolfpaw - Dale Corse: "RE: djbdns"
- Reply: Wolfpaw - Dale Corse: "RE: djbdns"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]