Could not resolve host: *.servicebus.windows.net for notification hub service

Rosa Aminta Salazar 0 Reputation points
2024-04-08T05:26:26.2+00:00

Could not resolve host: *.servicebus.windows.net related to a Notification hub name-space. I tried to use GET/POST Apis, curl, etc. commands and doesn't works.

I have tried making changes to the Notification name space like adding tags, refreshing keys, changing payment plan but it didn't works

Also, when I execute "az notification-hub namespace show" I find out that the "Status" of the name-space was Disabled, so I use "az notification-hub namespace update" to change it to "Active", it changes the Status but the DNS still doesn't work

Additionaly, if I execute "az notification-hub namespace check-availability" I find out the name-space appears available, but I can see it in the Az Portal, same tenant, suscription, resource group. I checked the resources.azure.com too, and the notification nam-space is there.

I looks like something is broken internally, how I can solve this without losing the current hubs associated with the notification name-space?

Azure Notification Hubs
Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
263 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Deepanshu katara 4,980 Reputation points
    2024-04-08T06:54:07.0566667+00:00

    Hi , Welcome to MS Q&A

    I think it seems DNS Issue , request you to perform below steps

    1. Test DNS Resolution Locally: Use the nslookup command-line tool to test DNS resolution locally from your computer. Run the following command:
           nslookup <namespace_dns_name>
           
      
      Replace <namespace_dns_name> with the DNS name of your Azure Notification Hub namespace. This command should return the IP address associated with the DNS name.
    2. Review Azure Portal for DNS Configuration: Double-check the DNS configuration of your Azure Notification Hub namespace in the Azure portal. Ensure that the DNS name is correctly specified and matches the DNS records configured in your DNS provider's control panel. You can find more information about configuring DNS names for Azure services in the Azure DNS documentation.
    3. Check Firewall and Network Settings: Review your network configuration, including firewall rules and network security group settings, to ensure that they're not blocking DNS queries to the Azure Notification Hub namespace. Ensure that DNS traffic is allowed through any firewalls or network security groups. You can find more information about configuring network security groups in the Azure Network Security documentation.

  2. brtrach-MSFT 15,256 Reputation points Microsoft Employee
    2024-04-10T16:01:47.1266667+00:00

    @Rosa Aminta Salazar We sent you a private message with next steps. Can you please review it? There should be a private message banner near the top of this page.

    0 comments No comments

  3. brtrach-MSFT 15,256 Reputation points Microsoft Employee
    2024-04-15T15:58:08.92+00:00

    @Rosa Aminta Salazar I'm glad that you were able to resolve your issue via workaround and thank you for your follow up in the private message. Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your workaround in case you'd like to "Accept " the answer.

    Issue: You were receiving the error, "Could not resolve host: *.servicebus.windows.net related to a Notification hub name-space"

    Solution: As a workaround, you recreated your Notification Hubs and the new environment did not encounter the scenario. We shared with you that if you encounter this issue again, please let us know and we can review what is causing this error.

    If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

    Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    0 comments No comments