Description of problem: The behaviour of DHCP reservations created by the Infoblox smart proxy currently does not match the behaviour of DHCP reservations created by the isc-dhcpd smart proxy: specifically, Infoblox does not seem to send the client host name in the offer (option 12, "host-name") unless the reservation contains an explicit DHCP option for that. In other words, setting the "name" field when creating the fixedaddress is not enough for Infoblox to send the "host-name" DHCP option. On the other hand, the isc-dhcpd smart proxy creates reservations with supersede host-name, causing the host name to be included in the response. A solution is to add an explicit "host-name" option to all fixedaddress records, making the Infoblox smart proxy behave more like the isc-dhcpd one. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Infoblox does not send host-name (dhcp client option 12) in the dhcp offer. Expected results: Infoblox send host-name (dhcp client option 12) in the dhcp offer. Additional info: There is a PR upstream implementing the change, in a way that foreman-proxy plugin creates the reservation on infoblox and sets the option 12.