On Thu, 2004-12-30 at 14:11, Suzzanah Harker wrote: > Hi again, > > Again I just want to know and will not implement > anything. A router in a LAN (with one server which > runs FC3) automatically assigns IP address to each > connected worskstation, so the router does all a DHCP > should do. What is the solution to get rid of IP > addresses for both servers and workstations in FC3 and > use domain names such as aaa.bbb.net instead ? Should > the server (FC3) be configured to be a DNS server or > still DNS and DHCP server ? > > S. You don't want to get rid of IP addresses. You want the ability to resolve names to IP addresses. There have been a couple of threads recently discussing DHCP and DNS. You may want to read through those threads for some good pointers. In general I recommend for small networks or home networks to assign static IP addresses to any servers or workstations you have and populate the /etc/hosts files with the names and IP addresses you have assigned. If you do have a router/firewall that acts as a DHCP server (which is good to have even if you don't use it for DHCP) setup the DHCP for a small range of addresses. This allows laptops or transient systems to connect to your LAN and get an IP address and other information needed to access the Internet. IMHO setting up DNS and DHCP to either statically assign addresses or to update DNS dynamically is complicated and for small LANs not worth the effort. Statically assigning IP addresses and populating /etc/hosts files is quick and simple. I do use DHCP for my laptop connections but everything else is assigned static IP addresses. Even in a corporate setting IMHO servers should be assigned static IP addresses. LANs that are used by laptop users should be segregated from other LANs. DHCP should only be run on those special LAN segments. -- Scot L. Harris webid@xxxxxxxxxx My mother drinks to forget she drinks. -- Crazy Jimmy
