-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 19 December 2003 18:25, Tom Hosiawa wrote: > I've know this has been covered before, but I'm still having trouble > setting up djbdns after reading a couple guides and all the relevant > posts here. > > Here's what I want to do: > I want the server to run dns for my domain name, say mydomain.ca > > server (192.168.1.2) -> > (a.mydomain.ca) > desktop(192.168.1.3) -> router (192.168.1.1) -> broadband (24.x.y.z) > (b.mydomain.ca) internet > laptop (192.168.1.4) -> > (c.mydomain.ca) > > >From what I've read I should setup: > > dnscache - to serve as a cache for my internal network (192.168.1) > dnscachex - to serve as a cache for my domain name to the outside world > tinydns - to serve as a name server for my internal network and the > outside world > > I think my main problem is using the wrong address in different parts, > and right know I have multiple services listening on one port: > > # netstat -nlp | grep udp | grep 53 > udp 0 0 192.168.1.2:53 > 0.0.0.0:* 20012/dnscache > udp 0 0 127.0.0.1:53 > 0.0.0.0:* 20010/dnscache > udp 0 0 192.168.1.2:53 > 0.0.0.0:* 20008/tinydns
I'd give your dns server a second IP as Stephan suggested, then put dnscache on one internal IP and dnscachex on the other altering any port forwards as needed, with tiny on localhost. You also might want to seperate your dns for internal machines on to a subdomain, I use home.mydomain.com. All your machines would then use the dnscache IP to resolve. - -- Mike Williams -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/43p7InuLMrk7bIwRAhgbAJ9VM/o4NPSr7c5jvN7plAp4KNOBNQCglb+l N4j7dNuAy+roAmn6cFldD3A= =HI9i -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
