> Here is my question. Naturally the router sits on an established > subnet and has an IP. The subnet is bsd.uchicago.edu (128.135.97.*). > I am trying to figure out what the domain of the LAN clients should be > (ie, the 192.168.1.* machines). Should they be in a subdomain of > bsd.uchicago.edu (eg milton.bsd.uchicago.edu), can they be anything at > all (eg, paradise.lost) since the outside world will never see them?
Yup, since the outside world doesn't have to see them you can make the domain whatever you want. What you may want to consider, though, is using bsd.uchicago.edu anyway and just making that box claim that it is authoritive for that domain. Add all of the addresses for your internal services as well as your external. Then bind 'named' (or whatever DNS server you are using), to the internal NIC only. Now, internal requests will never leave your internal network and you don't have to futz with resolve.conf and no one on the outside of the network will be able to query it. The downside to this is that you have to maintain two seperate DNS servers, one for the public world and one for your internal private network. > If they have their own subdomain (milton.bsd.uchicago.edu for the sake > of argument), then they will be on a different domain than the > router/DNS server, right? Since the DNS server is in the domain > bsd.uchicago.edu.... They are just name mappings. You could put the host in both if you wanted to: hostname.milton.bsd.uchicago.edu and hostname.milton.bsd.uchicago.edu. However the authoritive server for bsd.uchicago.edu will have to delegate the subdomain milton.bsd.uchicago.edu to the appropriate server, which sounds like a lot of complication for what you are trying to do. Cheers, sach -- /* Sach Jobb [EMAIL PROTECTED] %s/windows/linux/g */ "As far as i'm concerned the two biggest hassles in the world revolve around DNS and girlfriends." -- (name undisclosed to protect the innocent)
