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
Identity Router DNS Requirements Number of Views DNS External Service Interaction in RSA Authentication Manager 8.x - False Positive Number of Views Upgrade a patch from Windows Share fails with error in RSA Authentication Manager 8 Number of Views IDR Cannot Register with Cloud Authentication Service with Explicit Proxy and DNS Does not Resolve Authentication Service … Number of Views RSA Authentication Manager 7.1 to 8.1 - Migrating to a New Hardware or Virtual Appliance Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
