4

I'm using Dock to create Windows containers that are visible to the LAN via a transparent network.

The container get's it's IP from our (Windows) DHCP server. Everything works fine except that the DNS Server that serves our network does not update after the container got it's DHCP lease.

I've already altered the dynamic update settings to unsecure and secure and also changed the DHCP servers behaviour that it must update DNS entries dynamically every time.

If I recreate this error on a new test machine (Windows Server 2016 SE) and let my docker container use the private network that the server is in, the servers DNS server is updated with the containers hostname

1 Answer 1

8

Most often when I see this kind of DHCP-not-updating DNS behavior, it is because the credentials that DHCP uses to do the updates have a problem.

To access the credentials screen - Open up DHCP, right click IPv4 protocol, select the "Advanced Tab", and then the "Credentials" button.

enter image description here

You should also make sure that the "Dynamically update DNS A and Ptr ..." option is checked on the DNS tab.

enter image description here

2
  • I had enabled the dynamic updates only for my IPv4 segment, but not for IPv4 itself on the production server. Thank you for the help! May 28, 2018 at 6:14
  • 1
    Glad to have been a help! May 28, 2018 at 15:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .