This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 86%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
We host a wordpress site on Azure and previously had configured it to use our custom domain URL. However, we wanted to disconnect that domain from this web app (and point the dns to another non-azure location) and reset the web app to use the original azure domain (mywebsite.azurewebsites.net). We have done that in Azure and through our dns provider. However, the azure domain is still getting forwarded to our new website and to the domain that we previously used with this web app. In azure it clearly indicates that the URL is now the Azure domain name, mywebsite.azurewebsites.net. Please help as we need access to our old wordpress site. Thanks!
Hi @Alfie Swartzbaugh ,
Have you checked http://dnspropagation.net/ to ensure that the CNAME is no longer bound your mywebsite.azurewebsites.net? I know propagation could take some time for changes to reflect.
Regards,
Ryan
Hi, I'm not sure what this is supposed to tell me. The CNAME record returns waws-prod-am2-033.vip.azurewebsites.windows.net for a bunch of locations. Forgive me but what can I learn from that? I click the link and get the message "Custom domain has not been configured inside Azure. See how to map an existing domain to resolve this." and "Client cache is still pointing the domain to old IP address. Clear the cache by running the command ipconfig/flushdns." I've flushed the dns but where do I go from there. Again, I just want to go to the original azurewebsites URL that was provided at the beginning. Thanks!
Thanks Ryan! As you identified, our hacked WP site had a built in re-direct and we located the code and neutralized it. It wasn't a dns issue after all. We will be more careful in the future. Thanks again!