Orion Failover Engine is designed to integrate with DNS technology where the DNS is itself integrated with the Active Directory. SolarWinds recommends that Orion Failover Engine is installed in an Active Directory Integrated DNS environment. For more information about Orion Failover Engine and DNS integration, please refer to the Related Information below. Domain Name System (DNS) provides efficient name resolution and interoperability with standards-based technologies. Deploying DNS in your client/server infrastructure enables resources on a TCP/IP network to locate other resources on the network by using host name-to-IP address resolution and IP address-to-host name resolution. The Active Directory service requires DNS for locating network resources.
SolarWinds recommends that Orion Failover Engine be installed in an Active Directory Integrated DNS environment.
In a standard DNS zone, there can be one primary and multiple secondary DNS servers. The primary will be the Start of Authority (SOA) server for that zone and the other servers will be secondary. When adding a new host record (e.g. new server is added into the zone) the record will be inserted only in the primary DNS server. The information will be available on the secondary servers during the replication process between the primary and secondary servers.
In an Active Directory (AD) Integrated DNS environment, all servers are updated within the AD through multi-master replication (a change on any one server will be replicated to all other Active Directory databases).
For instructions on how to convert to an Active Directory Integrated DNS environment, please see the Related Information below.
When installing Orion Failover Engine in a WAN configuration, Orion Failover Engine automatically creates and configures the tasks needed to run DNSUpdate.exe. SolarWinds Orion Failover Engine Setup gathers the required information during the installation process and uses that information to configure the DNSUpdate task.
If Orion Failover Engine was initially installed in a LAN configuration and then later changed to a WAN configuration or problems are encountered with the operation of DNSUpdate.exe, please refer to SWREFID-1939 'How to Correct Problems when DNSUpdate Encounters secondary DNS Servers with Orion Failover Engine’ for information about how to configure the DNSUpdate task.
SolarWinds recommends that if the current environment is not Active Directory integrated, that migration to Active Directory integrated be performed prior to installing any Orion Failover Engine solution. Please see 'Related Information' below for Microsoft Knowledge Base articles for procedures on how to migrate to an Active Directory integrated environment.
In the event that Active Directory integration is not possible or not desired, the DNSUpdate utility can be configured to update specific DNS servers when identified by IP address.
To update DNS servers using the DNSUpdate utility in a non-Active Directory integrated environment, follow the steps below:
DNSUpdate.exe -ns 10.0.0.1 -r 172.16.0.1 -a 172.17.0.1 -name thehost -domain bla
| ||Update this Domain Name Server|| |
| ||Remove this ipaddress|| |
| ||Add this ipaddress|| |
| || |
Name of the server
| ||Domain Name|| |
In some cases, when updating standalone Windows-based DNS Server and due to non-AD membership of servers, account used to update DNS was throwing access denied error. You can see the error when running DNSUpdate in debug mode (add
-d option in command line):
Command failed: ERROR_ACCESS_DENIED 5 (00000005)
To work on that you will have to use following command on the FoE server
dnscmd.exe /Config /RpcAuthLevel 0