Why doesn't the virtual hostname resolve?
This topic applies to all Orion Platform products except for SolarWinds ETS.
This Orion Platform topic applies only to the following products:
ACM — APM — DPAIM — EOC — IPAM — LM — NAM — NCM — NOM — NPM — NTA — SAM — SCM — SRM — UDT — VMAN — VNQM — WPM
If your virtual hostname does not resolve, use the following information to troubleshoot this issue.
Are you using the correct IP address of the DNS server?
Ensure you are using the correct IP address of the DNS server for your DNS zone.
Are you using the authoritative DNS server's IP address ?
If you use the DNS server where the secondary zone is hosted, it is overridden when syncing with the primary zone.
Do your credentials have sufficient privileges?
Your credentials must be able to add or update host entries on the selected DNS server.
Can you connect to the DNS server?
You must be able to connect to the DNS server so the software can resolve the virtual hostname.
Do your firewall settings allow connections between your DNS server and your Orion server, including any Additional Web Servers?
You must be able to connect to the DNS server from your Orion server and any Additional Web Servers.
Can your web server resolve entries from the DNS server?
Verify that your Orion server or Additional Web Server is allowed to resolve host entries from your selected DNS server.