Ms dns not updating
Using an update client with your Remote Access (Dyn DNS Pro) or Dyn Standard DNS hostname allows you to make sure you can always reach your home network, because it makes sure that your hostname is always up-to-date with the latest IP address.
The update client runs in the background, so once you have it properly configured you don’t have to worry about it; you only need to remember your hostname to reach your files and services.
The basic crux of the issue is that MS DNS uses Kerberos for authentication to update DNS records, while ISC DHCP, out of the box, supports TSIG [for BIND].
Unfortunately, as they are all third-party products, you’ll need to contact the manufacturer for support with the device. If your host was blocked for abuse, it probably wasn’t something that you did intentionally.
Hosts are blocked to prevent our system from being flooded with unnecessary updates from broken or misconfigured update clients.
If the problem description is one of the following: ”Timeout establishing TCP connection” ”Error connecting...” ”Error: 10054 The connection is reset by remote side” Make sure that any firewall between the primary and the secondary servers allow TCP connections to port 53.
If your primary DNS server is behind a NAT router (as seen from the secondary server), make sure that you use the public IP address of the router and that port 53 TCP is correctly mapped to the private IP address of the primary DNS server on that router. If the problem description is ”RCODE 5 Refused...”, check the reference knowledbase article about this below.