Thanks no, the DHCP & DNS server do not need to be on the same box, but you do need to get the credentials right. (or you hopefully mangled them before posting...;) that's the whole point of including those files, so that the base config can be spread around without the keys. Do you wonder if your IT business is truly profitable or if you should raise your prices?
Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. "connection refused" Do you have a firewall blocking the update?
We default to the # behavior of the version 2 packages ('none', since DHCP v2 didn't # have support for DDNS.) ddns-update-style interim; ignore client-updates; # Overwrite client configured FQHNs ddns-domainname ""; ddns-rev-domainname "rev-0.2.16.172."; # option definitions common to all supported networks...DNS traffic is UDP/53, but zone transfers and I think dynamic updates come in on TCP/53, make sure IP tables is allowing both UDP and TCP 53 on the nameservers. Try allowing the update in Bind based on the IP of the DHCP server rather than the key, just to eliminate any problems with the keys: allow-update ; obviously change the IP to the same as your DHCP server.Do this in each zone definition you want it to update in I took at look at the DNS zone file but there was nothing in there.I was expecting the hostname to show up in the zone file? "connection refused" Aug 18 cortex dhcpd: Unable to add forward map from Apple TV.