Dhcp server not updating dns records
Those records have an ACL on them to stop registered records from being hijacked by other hosts.
@Roger Lipscombe There is no generic downside that I can think of, but I can't really say if there's a downside for your situation. It might be easier to drop your scope lease time really low, then delete all the dynamic DNS records and let them get re-created.If you're waiting on DNS scavenging, there's no fast way to do it.Hi Community, my SG300 is configured in L3 Mode in my Homelab and the DHCP Server feature is enabled. As DNS Server I've configured a bind9 server under raspbian wheezy. I was trying to configure this in my lab and was getting unexpected GUI input results that did not affect the packets at all. The Default Router IP Address (Option 3), the DNS Server IP (Option 6) and the Domain Name (Option15) are also configured. Clients get their IP Configuration inclusive Router, DNS and Domain Name information.Just let it ride until you're seeing id 2501 events in the DNS Server event logs.
I'm afraid that you're going to have to approach this from the client end.
If the clients happen to pick up their IP from the server then all is fine but if they get it from the router's DHCP then the DNS record on the server does not get updated even though dynamic updates is set to 'nonsecure and secure'.
This is on the same subnet but a different IP range.
What this means in practice is the following: This means the DHCP server computer account will own certain records in DNS, such as the PTR records and even some A records for older hosts.
(However, it's unlikely that you would have many NT 4.0 hosts in your environment.) This can cause the following two problems: For this reason, DHCP servers could be added to a group called Dns Update Proxy.
Is there any reason you wouldn't just have the router provide DHCP at all times?