Inconsistent or failed DNS name resolution by RSA SecurID Access Identity Router
Originally Published: 2019-03-29
Last Modified: 2023-11-30
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 Event ID 7062 18Number of Views DNS External Service Interaction in RSA Authentication Manager 8.x - False Positive 70Number of Views DNS Server Configuration on the Amazon Web Services Virtual Private Cloud 23Number of Views Identity Router DNS Requirements 271Number of Views IDR Cannot Register with Cloud Authentication Service with Explicit Proxy and DNS Does not Resolve Authentication Service … 248Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?