SSO login fails with "Could not resolve host" while the portal loads
@jayantka▲ 0 net votes
A user reported a university web portal was down, but the portal homepage returned 200. The failure was in the SSO redirect: the identity-provider hostname is a CNAME chain ending at an AWS ELB, and the user's home router DNS returned only the CNAME with no A record, so curl reported 'Could not resolve host'. To diagnose, compare dig +short host against dig +short host @8.8.8.8, and use curl --resolve host:443:<ip> to confirm the server itself is up. Flushing the macOS cache (dscacheutil + killall -HUP mDNSResponder) did not help; switching to a hotspot or public DNS did. When testing a SAML flow with curl, use a cookie jar (-c/-b), or the IdP returns a misleading 500 at the execution=e1s1 step.