That would make sense, but then tym0's reply to edvinasbartkus doesn't make any sense. It would be like saying: "It seems that DNS is not affected, only hosting." and the reply being: "Yeah, but it seems that hosting is affected as well"
Web redirects are usually not called web hosting in the dns industry, even if it technically operate just like any website. It is more like an attached service for a customers dns.
It is similar how the web interface for email has technically nothing to do with the email infrastructure and email protocols, but as a service it is packaged together with email.
It's not DNS alone. In the Gandi UI you can set up a so called "web redirect" which results in an A record pointing to one of their http servers that does the actual 301 redirecting. If that http server is down, the redirect won't work.
Yes it was badly phrased from my part, I should have said:
"My DNS record for www.example.com works but the web redirection I have from example.com to www.example.com doesn't work."
Maybe that is what the issue is? Some, well many, DNS providers provide value add transparent additional features like redirect and email. If their web infrastructure is down then that might not work even though the core DNS shit does.
CNAME is aliasing, not redirecting. If www.$domain.com is CNAME for $domain.com, loading www.$domain.com will make you remain on www.$domain.com, not redirect you.
