On Tuesday 08 June 2004 23:59, Koenraad Lelong wrote:
I am a noobie when it comes to configuring DNS - some guidance is appreciated.
I am reading the DNS info in the 9.1 administration guide. It talks about setting up zone files where one ends up hardcoding the IP addresses for each hostname on the network. That seems to defeat the purpose of DHCP though. I'm currently using a Linksys firewall as a DHCP server for my Windows clients.
I am setting up a SuSE Pro 9.1 server that will serve two main purposes: - Samba file and print sharing; - CVS source code server.
We currently only have six users. I would really like to get rid of the host files that I have been using on each server and workstation (servers Linus, workstations Windows 2000/XP). I think I need to setup a caching DNS server, plus 1 zone that identifies my local network servers and workstations.
But as I said above, that seems like it defeats the purpose of DHCP. What am I missing.
You are missing the fact that you don't need a DNS server at all. Forget it. Use the Linksys to serve IPs by DHCP, OR if you prefer set up the SuSE box to do the DHCP. Linksys usually supplies DNS services, and you can tell it to just pass it thru if you want. With SUSE serving IPs, it can also issue the IPs of DNS servers. Just set up the SuSE dhcp server to use your ISP's dns server. Want Static IPs for some machines? SuSE dhcp server can be set up to issue specific IPs to specific MacAddresses. In the windows world you just use machine names for in-house lookups. You really haven't made a confincing argument that you need a DNS server. -- _____________________________________ John Andersen