Dns not updating ip addresses
At the same time, Active Directory servers support DNS aging and scavenging, which means that stale DNS records might be removed from AD after a period of inactivity.While DNS scavenging is not enabled on Active Directory servers by default, the SSSD should support this use case and refresh its DNS records to simulate the behavior of Windows AD clients and keep their address records from being removed if scavenging is used.By default, this will point to the IP address for your 1&1 Web Hosting package however you can always change this so that the domain points to a different IP address.
This section provides a brief overview of how Windows clients may update their DNS records and how scavenging is configured and performed in a Windows domain.
You will need to update the IP address with your current DNS host.
Select Other IP address and enter IPv4 and optionally the IPv6 address into the provided text boxes. All DNS changes, though live on the 1&1 Server within minutes, may take up to 1 hour to be fully updated and recognised by all servers/computers on the Internet.
Contrary to IPA dynamic DNS update that generates the PTR record in the bind dyndb plugin, AD wouldn’t update the PTR record on its own when only A/AAAA record is updated.
To be able to keep the forward and reverse zones in sync, the AD dynamic update message would also include updating the PTR records.
Search for dns not updating ip addresses:
During design discussion, it was decided that the new options should be not include the provider-specific prefix but rather be provider agnostic to ease sharing the code and possibly allow other providers to use dynamic DNS updates as well.