John, You can make the domain what ever you want. In fact I would stay away from makeing it a subdomain of a larger domain that you don't have any control over. That could lead to problems.
If you did make it milton.bsd.uchi.edu the lookup would ask the authoritative server for uchicago.edu and that machine would point to another server (yours) responsible for the milton subdomain. So there is a bit of an administrative hit there... you would have to find a nice sysadmin that would do that for you. -e On Mon, 22 Oct 2001, John Hunter wrote: > > I am setting up a linux firewall router which runs a DNS server. This > is my first time so be gentle. > > The router will service a LAN on 192.168.1.*. > > 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? > > 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.... > > Clarifications welcome. > > Thanks, > John Hunter > _______________________________________________ <majcher> i forsee a successful porn career ahead of you.
