Inconsistent or failed DNS name resolution by RSA SecurID Access Identity Router
Originally Published: 2019-03-29
Article Number
Applies To
Issue
- Name resolution by Identity Router is failing inconsistently.
- Running nslookup fails when not specifying nameserver, but may succeed if a particular nameserver is specified.
- If the Identity Router is configured to communicate with Authentication Manager there may be errors in the symplified.log similar to:
Unable to resolve the Host:<AM_FULLY_QUALIFIED_HOSTNAME>, ignoring it
Note: An IDR to Authentication Manager test may also fail under these conditions.
Cause
Resolution
Related Articles
DNS External Service Interaction in RSA Authentication Manager 8.x - False Positive Number of Views To prevent installation failure if Windows NT Domain controller is not present. Number of Views RSA SecurID Authenticator 4.1 for iOS and Android Quick Start Guide (Italian) Number of Views DNS Server Configuration on the Azure Virtual Network Number of Views Identity Router DNS Requirements Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
