On 2011-10-05 12:15, Stack Kororā wrote:
> * I would like a server that serves up DHCP and DNS on a isolated LAN
> that does *not* have internet connection (one Ethernet cable from
> servers to giant bank of switches).
> * There will be three subnets: one is manually assigned 10.1.1.x, the
> DHCP server will have 10.1.2.x, and the DHCP/TFTPd server will server
> DHCP on 10.1.3.x.
> * All hosts should resolve their hostnames (and FQDN's! ) in the DNS
> regardless of if they are assigned via DHCP, manually, or PXE booted.
> * I would _really_ like to have a second server that is "failover" in
> case the first goes down, but I need the first working before I worry
> about that.
>
<snip>
>
> I have a minimal 6.1 install with DHCP and BIND DNS. Setting up the DHCP
> is now pretty easy; I can reinstall the minimal OS and DHCP pretty quick
> now (it may not be 100% correct but it works). I still have not messed
> with the PXE booting on the DHCP yet, but I can get a system to receive
> a DHCP address on the 10.1.2.x network and talk to the systems I
> manually set on the 10.1.1.x and 10.1.3.x networks.
>
> Right now, DNS (using the named service BIND provides) still doesn't
> work right. The closest I have gotten was by accident. Some how (not
> sure how as it was an accident) I managed to get the DNS server to work
> with the DHCP server. So the two systems that were setup to get a
> 10.1.2.x DHCP addresses could ping each other by hostname only. EG:
> `ping host1` and `ping host2` would work and it claimed it was resolving
> to 'host1.project.local' but `ping host1.project.local` would fail as
> hostname not found. Not only was this by accident, but it was REALLY
> slow. It was at least 10 seconds from the command being run to the first
> ping. However, none of the other systems were resolvable and they
> couldn't resolve the DHCP systems. I restarted the named service and
> then it all stopped working. I can't ping anyone by host name anymore.

I suggest you give some more details about your named and dhcpd 
configurations.  Also remember that if your network is not connected to 
the Internet at all then you need to run your own root nameserver to 
make DNS work reliably.

-- 
Garrett Holmstrom