We welcome user feedback and feature requests!

Improve DNS verification procedure for vendors that host sites others point to

We host some services and our clients point to them using CNAMEs. We want to move from cloud services to web apps but right now it's a massive pain. We have to notify all our clients to first add TXT records for approval, then approve and then ask all of them to switch to new CNAME. Asking clients to do any DNS changes is already a problem and now we have to coordinate with all of them to first add txt records and then point to new service. This makes the whole process really painful even though we are already running all of those domains inside cloud services. Is there any migration mechanism that is less painful than what I described?

Thanks

8 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Vlad Kosarev shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Vlad Kosarev commented  ·   ·  Flag as inappropriate

        Google found multiple ways of verifying domain (html file, html tag, tracking code)
        Why couldn't this be done using a file/tag or something like App Insights tracking code? If a site is already fully running on Azure in a service on the same account it has got to be possible to verify based on that too. Where there is a will, there is a way.

      Feedback and Knowledge Base