Notification Namespace Push Error "The remote name could not be resolved"

Jim 25

This may or may not be related to https://learn.microsoft.com/en-us/answers/questions/1283383/missing-notification-hub as both problems have recently occurred.

The only other background information is that my April Visual Studio monthly credit of $150.00 was maxed (testing Azure Cognitive Services did that). But now it's May, and my remaining credit is $149.99.

The problem is any connection to a previously working Notification Hub Namespace service endpoint throws the error "System.Net.WebException: The remote name could not be resolved: 'xxx-yyy-zzz.servicebus.windows.net'" (the xxx-yyy-zzz is a replacement for the actual name).

This is happening on multiple Notification Hub Namespace originating from different servers in different physical locations.

What has caused this and how do I fix it?

Luke Murray 10,526 Reputation points MVP

2023-05-14T20:06:02.79+00:00

Hi, Jim.

This may be a bug, caused by the reactivation of your resources - try to make a minor change to one of the namespaces, then back again (for lack of better terms, to kick the resource into gear) and retry and let me know how you get on. Sometimes a resource state can be locked, and making an update/modify on a resource can resolve the issue.
Jim 25 Reputation points

2023-05-16T01:19:14.3933333+00:00

I tried adding a Tag, leaving it for a day then deleting it. Is this something better to try?
Chan, Andrew G 0 Reputation points

2023-11-02T19:43:35.8666667+00:00

Any luck? We have a deployment out, but the namespace got disabled due to a payment failure. We fixed the payment and re-enabled the namespace, but the xyz.servicebus.windows.net endpoint is unreachable. Sending test notifications from the Azure portal works, but nothing from external servers. I'm wondering if the DNS needs to somehow get refreshed.
Jim 25 Reputation points

2023-11-02T20:51:47.1366667+00:00

I've had no luck getting them back online. The only "solution" I've found so far is to delete both the namespace and hub, recreate them and ask all users to check their settings.
100jecki 0 Reputation points

2024-01-09T14:19:41.3333333+00:00

I am in a similar situation. Account blocked due to reaching payment limit. The namespace has been manually activated. In the Notification Hub Namespace view, the Notification Hub tab shows the missing Hub but the direct Notification Hubs view does not show this Hub. Does anyone have any idea what can be done about this?