-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BMC is not extracting Domain Name & configuring it on BMC #47
Comments
@ratagupt @wak-google The issue here is that the /etc/resolv.conf is not getting the PS: The DHCP supplied DNS server IP is updated as expected for |
System already has the systemd fix systemd/systemd#8174 |
When the interface is DHCP enabled, domain-search value 119 is not requested by the DHCP client. This commit adds the UseDomains option to network file so that when the DNS is enabled, the domain-search option is requested via DHCP REQUEST, and search list provided by DHCP server are pulled to the DHCP lease and the resolv.conf Fixes openbmc#47 Tested by: 1.Enable DNS option at BMC and check the DHCP REQUEST packet for option 119 2.Verify the list 'option domain-search' at the DHCP server is fetched by the DHCP lease file at BMC 3.Verify the same list is added to the search list at resolv.conf Signed-off-by: sunharis <sunharis@in.ibm.com> Change-Id: I2f6ca7236bf3b5e7d3ded9294b8372d95ac50ac6 Co-authored-by: sunharis <sunharis@in.ibm.com>
Problem Description
BMC is not extracting Domain Name & configuring it on BMC
Steps:
Enable UseDomainName dhcp property.
curl -k -H "X-Auth-Token: $bmc_token" -X PATCH -D patch.txt -d '{"DHCPv4" : {"UseDomainName":true}}' https://$bmc/redfish/v1/Managers/bmc/EthernetInterfaces/eth1
Check whether property is set or no using following command:$bmc_token" -D get.txt -X GET https://$ {bmc}/redfish/v1/Managers/bmc/EthernetInterfaces/eth1
curl -k -H "X-Auth-Token:
Send DHCP request and see if bmc uses domain name offered by DHCP server:
Expectation:
resolv.conf should get updated with line like below:
search something.com
The text was updated successfully, but these errors were encountered: