RE: DHCP posted 03/23/1999
For learning purposes, it just fun to make a router pretend to be a DNS/DHCP
server or make a DNS/linux server pretend to be router.
Of course, in implementing network services for your company, I agree,
follow best practice.
From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf Of
Howard C. Berkowitz
Sent: Monday, March 22, 1999 4:55 PM
Subject: RE: DHCP
*** Tom Thomas wrote,
>I hate to disagree with you there berk but routers can and do act as dhcp
>servers if properly configured.
Even if they can, is it really a good practice? I think the trend is to
link DHCP and DNS. Both of these services are apt to need a large amount
of memory, and, especially in the case of DNS, have a great many database
entries that are not frequently used.
Routers are optimized for route lookup and forwarding. . A Cisco 12008
will be inferior to a Pentium II for a database server. I always wonder
about the motivation for running such things as Microsoft RRAS (Steelhead,
or Microsoft's OSPF -- which is a port of Bay RS code). Why should a
general database machine make a good router?
DNS, and for that matter DHCP, services are not terribly CPU intensive.
One interesting approach is to recycle 386 and 486 machines as DNS cache or
secondary servers, possibly with DHCP. You would run these older machines
under LINUX or some other free UNIX that is much less resource intensive
than Windows NT, and essentially treat them as throwaways.
To remove your name from the mailing list send a message to
Majordomo@xxxxxxxxxxxxxx with the body containing "UNSUBSCRIBE CISCO"
To remove your name from the mailing list send a message to Majordomo@xxxxxxxxxxxxxx with the body containing "UNSUBSCRIBE CISCO"