none
Failure to resolve CNAME record. RRS feed

  • Question

  • Web.com is looking for CNAME validation for a domain for a certificate.

    I setup the following:

    B452EB53F554427C4B3D8174FDC0B937.domain.com. points to a3a1e980b5f6cc3dd489cf234231a840.c16a24f33cffb9e7af56a53fa25262b1.comodoca.com.

    (digits and domain.com have been changed to protect the guilty)

    This does not resolve.  I get a response but it doesn't contain the data.

    > B452EB53F554427C4B3D8174FDC0B937.domain.com.
    Server:  ns2.MYDOMAIN.com
    Address:  mynameserverIP
    Name:    B452EB53F554427C4B3D8174FDC0B937.domain.com
    >

    I tried this on another ADDNS server in a different forest and get the same results.

    Is web.com just high?


    -=Chris

    Friday, October 27, 2017 11:53 PM

All replies

  • Hi,

    I suppose you have a wrong operation. We don’t have these usages in DNS CNAME record.


    Try to use this method to resolve the cname: ping -a cname

    Below is an sample:

    Best Regards,
    Frank



    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, October 30, 2017 8:03 AM
  • I don't follow.  Are you saying you can't use NSLOOKUP to resolve a CNAME?

    PS C:\Windows\system32> nslookup
    Default Server:  pr-dc17.progent.com
    Address:  162.211.28.17
    > autodiscover.outlook.com
    Server:  pr-dc17.progent.com
    Address:  162.211.28.17
    Non-authoritative answer:
    Name:    autodiscover-namnorthwest3.outlook.com
    Addresses:  2603:1036:102:e0::8
              2603:1036:804:1::8
              2603:1036:902:90::8
              2603:1036:102:52::8
              2603:1036:405:5f::8
              2a01:111:f400:30be::8
              2603:1036:4:29::8
              2603:1036:906:83::8
              2603:1036:804:21::8
              40.97.120.56
              40.97.161.40
              40.97.149.152
              40.97.118.168
              40.97.185.8
              40.97.127.136
              40.96.32.40
              40.97.129.136
              40.97.121.24
    Aliases:  autodiscover.outlook.com
              autodiscover.geo.outlook.com
              autodiscover.outlook.com.g.outlook.com
    >


    -=Chris

    Monday, October 30, 2017 7:35 PM
  • Hi,

    Of cource, nslookup can resolve CNAME. We try ping utility is just a tests.

    Best Regards,
    Frank


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 31, 2017 3:01 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 7, 2017 10:46 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,
    Frank

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 14, 2017 7:45 AM