On Mon, 28 Jul 2008 04:06:00 PDT Akhilesh Mritunjai <[EMAIL PROTECTED]> wrote:
> Hi
>
> You have two options:
I missed the original question, but there are lots of suboptions here
that might swap the two cases around depending on the goals.
> 1. Hard Way: You will have to make one computer the DHCP & DNS server and
> configure the DHCP server to configure the DNS server when new IP is
> assigned. Disable the DHCP & DNS on the router/modem. Howtos are available on
> net, but it's usually not worth the pain.
Note that your DHCP & DNS server has to have a static IP address even
if nothing else does. Getting the popular DHCP & DNS to do this is
hard. Using dnsmasq - a combined DHCP & DNS server - that is designed
for this situation makes it easy. If no one has ported dnsmasq to
solaris yet (I haven't loked yet), that may be hard.
> 2. Easy way: Configure static IP for all "usual" machines. Configure the
> router to start DHCP addresses above a certain range (eg reserve 192.168.100
> so that static & dynamic ones don't clash). Then use a /etc/hosts file on
> each machine with the name & address mapping. A typical one looks like this:
>
> 192.168.1.5 spooky.localdomain spooky
> 192.168.1.6 blah.fu blah
If you never want to contact most of the machines on your network by
name, then this is the easy way. That's not true for me - we don't use
windows boxes for *anything*, so everything can be ssh'ed or vnc'ed
into, so there's a reason for pretty much everything to have a name in
dns. Given that most of them install out of the box expecting DHCP and
willing to advertise a name if you give it one, then this is the hard
way.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
opensolaris-help mailing list
[email protected]
