Query: Networking Settings

[Mike64]

Good morning,

In HPE OneView Settings > Networking, I need to set preferred and alternate DNS servers.

I cannot set these without also setting the 'Appliance host name' in fqdn format.

The appliance is not a member of a domain so does not have a fqdn.

I tried adding a DNS A record, in the domain, and then adding the appliance host name in fqdn format but this did not work.

As I need to successfully configure the appliance host name, before I can configure 'Remote Support', I'm stuck.

If anyone has successfully navigate this issue, and can provide a resolution, it would be greatly appreciated.

Thanks,

Mike

[Sahana_S]

Hello @Mike64 ,

In HPE OneView, configuring DNS settings and setting the appliance host name in FQDN format is a necessary step for enabling features like Remote Support. If your appliance is not part of a domain and does not have an FQDN, you can still assign it a hostname in FQDN format to meet OneView's configuration requirements.

1. Manually assign an FDQN by choosing hostname and domain name.
2. In your DNS server, create an A record for the hostname and associate it with the IP address of your HPE OneView appliance.
3. On a client system, test DNS resolution to ensure the FQDN resolves to the HPE OneView appliance's IP address. 
4. Set the Appliance Host Name in HPE OneView.

You may refer to this document for information on Configuring HPE OneView appliance host name and DNS, also refer to this document.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

Thanks and Regards,
Sahana S

[support_s · Accepted solution]

System recommended content:

1. HPE OneView 10.1 User Guide for HPE Synergy | Change the Appliance network settings

2. HPE OneView 10.1 User Guide for VMs | Settings: Appliance Networking

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Mike64]

Many thanks for your answer Sahana.

I tried this solution without success, previously, but this was because the appliance didn't have network connectivity to the DNS servers I had entered.

When I entered a DNS server, the appliance did have access to, it worked.

[Sahana_S]

Hello @Mike64 ,

It is glad to know that you query has been resolved.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thanks and Regards,
Sahana S

[ChrisLynch]

The reason why OneView attempts a DNS connection is to validate what you entered is reachable.  Otherwise, why attempt to configure a setting that will never work correctly?  Additionally, you do not need to create a DNS A record for your appliance.  It is recommended you do, but not required.  During the network settings validation task, the appliance will perform both a forward and reverse DNS lookup to the specified DNS servers.  If either fail, you will only see a warning alert, and you can safely clear.  In the past, we had many customers use our products, believe DNS was configured correctly (client and server side), only for it not to be and causing communciation problems.

[zayanhani]

hey Mike

I ran into something similar with OneView it seems like the appliance really wants an FQDN even if it’s not on a domain. one workaround i saw was to just create a “fake” domain locally, like appliance.local, and point it in your local DNS so it resolves to the appliance’s IP. that satisfies the FQDN requirement and lets you set the DNS servers.

not perfect, but it got remote support working for me. curious if anyone has a cleaner method though, especially for environments that truly are not in a domain.

[ChrisLynch]

When you specify DNS servers, it is expected to provide an FQDN in any compliant format.  As I stated in my reply above, the appliance will then attempt to perform DNS lookups for what you provided to set the hostname and IP address have the appropriate DNS A and/or AAAA records.  If the DNS lookups are not successful, it will not impact the state of the appliance.