Sbs 2016 dhcp not updating dns
Visit Stack Exchange We use windows server 2003 for DNS on our network.The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.DHCP is on a 2012 R2 failover platform and I can see an error 1340 in the system event log when it fails to update the A record.I had a prior issue where the legacy DHCP server was set to use credentials for registering the records and I had not configured that in the new environment which was resolved in large part by updating the ACL on the record.Is this just a "bug" in SBS2008 whereby Microscoft simply doesn't like supporting non-Microsoft systems, or am I doing something fundamentally wrong?Please see this: and this: Sorry for the delay - this question fell off my radar.Is this just a "bug" in SBS 2008 in that it will only DNS register Windows-only DHCP clients?If so, I guess I'll live with the DHCP reservation solution.
What do I need to do to get this host into DNS (host 192.168.0.50 is another Linux host showing up in the DHCP leases, but not in the DNS) Yes, as stated in my initial post, I already have "Always dynamically update DNS A and PTR records" set, but it's not doing it. Not sure where to find the user privileges settings, but I believe those are set to the system administrator. If DHCP is set up update DNS, what would privileges be needed for?
Jeffery Kane, that link seems to have done the trick!
The short answer is to put the local/client hostname in the /etc/rc.d/rc.inet1as: DHCP_HOSTNAME="thishost" Normally I do mention distro and version, but for whatever reason I didn't think this was an issue on the Linux side.
I know I can put a static IP into the DNS list for this host, but I'd rather use DHCP.
For DHCP DNS, I have "Enable DNS dynamic updates according to the settings below:", "Always dynamically update DNS A and PTR records", "Discard A and PTR records when lease is deleted", and "Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0)".The DHCP lease obviously does have both the IP and the hostname, so I'm puzzled as to why it is not updating the DNS. Jeffrey Kane: Just create a DHCP reservation for this machine and it will solve your problem.