I have a cname record to a dyndns address. This has worked fine in the past, but now if I use the cname error I get a 502 error from IIS 7. The dyndns address works fine and so does the actual ip address. Any ideas on what would cause this?
Answer
Found the root cause. I had an old rewrite rule at the server level for that domain name. I had only checked the rewrites at the website level. The domain it was pointing to is now gone, hence the 502 bad gateway message. I disabled the rule and all is fine.
Comments
Post a Comment