Is DHCP lease expriring years from now okay?
Posted
by
sharptooth
on Server Fault
See other posts from Server Fault
or by sharptooth
Published on 2012-09-25T08:13:41Z
Indexed on
2012/09/25
15:39 UTC
Read the original article
Hit count: 303
I'm reviewing Azure web role logs and there's output from ipconfig /all
IPv4 Address. . . . . . . . . . . : 10.61.145.37(Preferred) .
Subnet Mask . . . . . . . . . . . : 255.255.254.0.
Lease Obtained. . . . . . . . . . : Monday, September 24, 2012 12:26:00 PM.
Lease Expires . . . . . . . . . . : Thursday, October 31, 2148 6:55:12 PM.
you see, the lease expires in year 2148 but my VM will likely not run for more than one month - when I deploy the new version of my code I first deploy it to new VMs, then switch traffic, then release the new VMs. In general such usage pattern is normal - VMs typically live from several dozen minutes to several weeks on Azure.
I suspect the lease that long will cause problems on the internal Azure network sooner or later.
Is such long DHCP lease okay or is it likely a misconfiguration?
© Server Fault or respective owner