The following forum(s) are migrating to a new home on Microsoft Q&A (Preview): Azure Active Directory!

Ask new questions on Microsoft Q&A (Preview).
Interact with existing posts until December 13, 2019, after which content will be closed to all new and existing posts.

Learn More

 none
Domain Verification Errors RRS feed

  • Question

  • Hello Azure Community,

    Upon trying to verify my domain in Active Directory I receive an error that states:

    Could not verify the domain
    Please try again. If the problem persists, contact support.

    I was curious to know if anyone else has received this error while trying to verify a domain within Azure Active Directory.

    I have double-checked to make sure my TXT records are valid.

    # dig @ns1.seven-labs.com hq.seven-labs.com -t TXT
    
    ; <<>> DiG 9.8.1-P1 <<>> @ns1.seven-labs.com hq.seven-labs.com -t TXT
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29918
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
    
    ;; QUESTION SECTION:
    ;hq.seven-labs.com.             IN      TXT
    
    ;; ANSWER SECTION:
    hq.seven-labs.com.      3600    IN      TXT     "MS=ms75626532"
    
    ;; AUTHORITY SECTION:
    hq.seven-labs.com.      38400   IN      NS      ns2.seven-labs.net.
    hq.seven-labs.com.      38400   IN      NS      ns1.seven-labs.net.
    hq.seven-labs.com.      38400   IN      NS      ns1.seven-labs.com.
    hq.seven-labs.com.      38400   IN      NS      ns3.seven-labs.net.
    hq.seven-labs.com.      38400   IN      NS      ns4.seven-labs.net.
    
    ;; ADDITIONAL SECTION:
    ns1.seven-labs.com.     3600    IN      A       138.91.176.183
    ns1.seven-labs.net.     3600    IN      A       138.91.176.183
    ns2.seven-labs.net.     3600    IN      A       137.135.216.61
    ns3.seven-labs.net.     3600    IN      A       137.135.101.199
    ns4.seven-labs.net.     3600    IN      A       74.208.45.82
    
    ;; Query time: 2 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Nov  5 20:42:39 2013
    ;; MSG SIZE  rcvd: 245

    As you can see from the lookup above, the TXT was returned without an error.

    Does anyone have any ideas?

    Thanks in advance,

    Sam


    Sam W. (http://sdw.seven-labs.com)


    • Edited by Samuel Walton Tuesday, November 5, 2013 8:47 PM Added Screenshot
    Tuesday, November 5, 2013 8:44 PM

Answers

  • Hi Sam,

    First, are you sure there isn't an existing AAD tenant with this domain? (For example, do you have this domain in Office 365?)

    Second, give it another shot. I can also see using http://www.digwebinterface.com that the TXT records are in fact there, perhaps it was a fluke in DNS propagation.

    Third, give it a go with PowerShell for Azure Active Directory. Use Get-MsolDomainVerificationDns -DomainName "hq.seven-labs.com" -Mode DnsTxtRecord to confirm that the TXT records it expects are the ones you set, and then run Confirm-MsolDomain -DomainName "hq.seven-labs.com".) If you get an error from PowerShell as well, do let us know what it says.

    Philippe


    Wednesday, November 6, 2013 9:50 AM