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 Troubleshooting Primary or Replica Hostname resolution 59Number of Views Identity Router DNS Requirements 268Number of Views RSA Certificate Manager security vulnerabilities for Apache - False Positives (CVE-2011-3368 / CVE-2012-0053 / CVE-2013-18… 73Number of Views DNS Resolution does not work on new installs 30Number of Views
Trending Articles
RSA Authentication Manager 8.3 Dell 630 and 230 hardware appliance loses ability to access keyboard when running PING 4.0 … RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Troubleshooting RSA MFA Agent for Microsoft Windows RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?