none
How to fix The requested service DNS name could not be resolved - Azure Search

    Question

  • We are facing some issues with Azure Search.

    The below error occurs exactly hourly.

    "The remote name could not be resolved: 'xxxxxxxx.search.windows.net'"

    and

    "The requested service DNS name could not be resolved""

    I don't know if is a Azure Search issue. Anyone have an idea how to fix it?

    Monday, May 13, 2019 1:41 PM

Answers

  • Hi Grace,

    Thank you for your help.

    I believe we found the problem. We posted the same problem in stackoverflow and another user faced the same situation yesterday. He directed us to the Azure Status History website.

    5/13
    Network Connectivity - Increased Latency

    The day and time coincides with the moment that the problems happened. This must be the root cause.

    The information is available at Azure Status History website (I can't send links with my account. Sorry).


    Tuesday, May 14, 2019 2:00 PM

All replies

  • Hi Wagner,

    I don't believe Azure Search has an issue but we can double check internally and get back to you. When did you start seeing this error? 

    Tuesday, May 14, 2019 9:30 AM
    Moderator
  • Hi Grace,

    Thank you for your help.

    I believe we found the problem. We posted the same problem in stackoverflow and another user faced the same situation yesterday. He directed us to the Azure Status History website.

    5/13
    Network Connectivity - Increased Latency

    The day and time coincides with the moment that the problems happened. This must be the root cause.

    The information is available at Azure Status History website (I can't send links with my account. Sorry).


    Tuesday, May 14, 2019 2:00 PM