Not sure if you're running Mac or Windows, but I experienced this issue on a Mac (Yosemite), and found the solution on Apple's discussions site.
no, it's Win7 64. I've reinstalled CC desktop and still the same problem.
Weird thing is that the apps themselves are still able to be updated manually (I updated InDesign this morning, the new CClibraries Panel keeps telling me it can't connect to Adobe Servers.
Ironically enough, I can sign into this forum with my Adobe ID but nowhere else!
1 person found this helpful
The problem is that the delegation from DNS parent zones is at fault. ims-na1.adobelogin.com is a CNAME to adobelogin.prod.ims.adobejanus.com, which is okay per se. However, if the delegation (glue records) for prod.ims.adobejanus.com are tested with a tool like RIPE NCC's DNSCheck Adobe's network operators should see what the problem is:
Essentially, (a) the parent zone lists a set of name servers that differs from the nameservers listed in the subzone, and (b) these nameservers are not authoritative for the subzone.
If you happen to use a DNS server (DNS resolver, aka DNS proxy) at your ISP which ignores such inconsistencies (like Google's 184.108.40.206), you're fine and can log in. However, if your provider's DNS server does notice, it won't answer the request. In particular, DNSSEC validating DNS resolvers will not accept lame delegations.
Adobe really needs to fix this. If I get a pointer how I could write to the guys in charge more directly than through this forum, I'd certainly do. This lame delegation prevents us (an ISP) from activating DNSSEC validation (which would be good thing to do), because our customers would blame us and not Adobe, even if we tell them.
In our effort to secure our internal DNS servers, we had implemented DNSSEC validation. Unfortunately, it seems that the validation prevents our users from validating with adobelogin.com. For the time being, we removed DNSSEC validation so that we don't stop our work effort. It's clear that someone from Adobe's DNS team is sleeping. Wake up!
I am too experiencing this issues and can't login from certain places.
It's unbelievable their IT team hasn't fixed this yet