Common host name www.servicebus.windows.net is not working

[sambitr]

Description

Hi There,

I was trying to use the istio wild card egress rule setup for our Azure resources.This needs common host names for the Azure resources. This works fine for the services like Key vault, Storage account, SQL server, who have common host name resolution working properly for host names: www.vault.azure.net, www.blob.core.windows.net, www.database.windows.net respectively.

But the same is not working for service bus: www.servicebus.windows.net. Is there any alternate common host available for this?

skrout@Sambit MINGW64 ~
$ nslookup www.vault.azure.net
Non-authoritative answer:
Server:  UnKnown
Address:  10.1.0.4

Name:    azkms-prod-eus-a.eastus.cloudapp.azure.com
Address:  20.62.134.229
Aliases:  www.vault.azure.net
          data-prod-eus.vaultcore.azure.net
          data-prod-eus-region.vaultcore.azure.net


skrout@Sambit MINGW64 ~
$ nslookup www.blob.core.windows.net
Non-authoritative answer:
Server:  UnKnown
Address:  10.1.0.4

Name:    blob.cys05prdstr23a.store.core.windows.net
Address:  20.60.4.97
Aliases:  www.blob.core.windows.net


skrout@Sambit MINGW64 ~
$ nslookup www.table.core.windows.net
Non-authoritative answer:
Server:  UnKnown
Address:  10.1.0.4

Name:    table.cys05prdstr23a.store.core.windows.net
Address:  20.60.4.99
Aliases:  www.table.core.windows.net


skrout@Sambit MINGW64 ~
$ nslookup www.database.windows.net
Non-authoritative answer:
Server:  UnKnown
Address:  10.1.0.4

Name:    cr4.germanywestcentral1-a.control.database.windows.net
Address:  51.116.248.0
Aliases:  www.database.windows.net
          dataslice2.germanywestcentral1.database.windows.net
          dataslice2germanywestcentral.trafficmanager.net

skrout@Sambit MINGW64 ~
$ nslookup www.servicebus.windows.net
*** UnKnown can't find www.servicebus.windows.net: Non-existent domain
Server:  UnKnown
Address:  10.1.0.4

During the egress rule setup the connection is working fine for KV and other resources, where the common host name is getting resolved. But the same is not working for SB. Example:

[2024-03-22T08:26:55.347Z] "- - -" 0 UH - - "-" 0 0 0 - "-" "-" "-" "-" "-" outbound|443||www.servicebus.windows.net - 172.0.0.41:8443 172.0.2.39:54428 dts-demo-dev-bus.servicebus.windows.n

[2024-03-22T08:35:01.017Z] "- - -" 0 - - - "-" 1254 8139 353 - "-" "-" "-" "-" "20.62.134.229:443" outbound|443||www.vault.azure.net 172.0.0.41:58384 172.0.0.41:8443 172.0.2.39:33964 dts-demo-dev-kv.vault.azure.net -

Actual Behavior

1. nslookup is not resolving the common host name for Service Bus

Expected Behavior

1. nslookup should resolve the common host name, like other Azure resources

[EldertGrootenboer]

Thank you for this suggestion. We are already planning some other changes around our DNS names, we will take this into account during those changes as well. There are no specific timelines to share yet, however we will update this issue as things are starting to take shape.

[EldertGrootenboer]

We have added this feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios.