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 68Number of Views To prevent installation failure if Windows NT Domain controller is not present. 14Number of Views RSA SecurID Authenticator 4.1 for iOS and Android Quick Start Guide (Italian) 8Number of Views Identity Router DNS Requirements 263Number of Views Troubleshooting Primary or Replica Hostname resolution 59Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?