Dual DHCP DNS Server 6.24 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Dual DHCP DNS Server 6.24 (Default branch)
# 1  
Old 01-20-2009
Dual DHCP DNS Server 6.24 (Default branch)

Dual DHCP DNS Server is a DHCP server combinedwith a caching DNS server that is sensitive to thenames that were allocated by the DHCP server. Ithas built in dynamic updates, and also supportsBOOTP PXE network booting and client specificoptions. It is self-configuring, doesn't requirethe creation of zone files, and uses little memoryand CPU time. Either one of the two services canbe turned off.License: GNU General Public License (GPL)Changes:
MAC range, vendor class, and user class filters have been added to the DHCP range section. DHCP replication has minor bugfixes.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies
Login or Register to Ask a Question
namepool(4)						     Kernel Interfaces Manual						       namepool(4)

NAME
namepool - DHCP server database DESCRIPTION
The namepool database provides joind with names that are available for dynamic assignment to clients of the DHCP protocol. For each DHCP server and domain name (NIS or DNS), the database contains a collection of names available for allocation to DHCP clients within those domains. One name plays a distinguished role - it is used as a prefix when the pool has been exhausted. Names are generated from the pre- fix by appending a number, 1,2.., and a trailing 'd'. The namepool file is read whenever joind starts. Names within the database must not be allocated to hosts which are not DHCP clients, and if the administration of a domain is shared between several DHCP servers, the name- pools that each has must be disjoint. Names may be added and removed from the namepool file. If a name is removed from the file it remains bound to the client to which it was allocated; if no such binding is in effect the name is excised from the server's pool the next time the server starts. Once a name is dynamically bound to a host it will never be reused even if that host subsequently acquires a new name, but there is no need to remove it from namepool. FORMAT Blank lines and lines beginning with a number sign (#) are ignored. A new entry must begin in column one and has one of the following for- mats: domain server domain server name_prefix The domain variable is the domain in which the names which follow are assigned. The server variable is the name or IP address of the server in charge of allocating these names to clients. The prefix variable is the prefix that will be used when the pool is exhausted. Succeeding lines contain one or more names for domains that are to be allocated by the server. Each of these succeeding lines must begin with at least one white space character. FILES
/etc/join/namepool RELATED INFORMATION
joind(8), join.ipaddresses(4) delim off namepool(4)