Networking
The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.
Virtual Network:
Traffic Manager:
Network Watcher:
If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.
-
Azure DNS needs DNSSEC support
DNSSEC is required to be able to secure your DNS requests. At the moment this is not available. We cannot move until our domains to Azure DNS untill these requirements have been met.
6,055 votesDNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
-
Azure should be its own domain registrar
Windows Azure should offer domain registrar services so users don't have to maintain our domain names with a separate company. This also has the potential to greatly streamline the process of setting up a website on Azure.
1,604 votesDomain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
-Rohin K -
Extend Azure DNS to support zone transfers so it can be used as seconday DNS
If Azure DNS supported zone transfers, then if could be used both as a reliable secondary DNS service, or as an external proxy service for AD split-brain, or on-premise hosted DNS configurations.
1,545 votesZone transfer is on our roadmap however not planned for CY 2019.
-Rohin K -
Provide a 301 (Permanent) redirect service for apex (naked) domains
Discussed in the Azure DNS docs: https://azure.microsoft.com/en-us/documentation/articles/dns-getstarted-create-recordset/#comment-2294403853
Right now, you must use a static IP address if you want to point an apex (naked) domain (e.g., mycompany.com) to a Cloud Service (e.g., mycloudservice.cloudapp.net). Static IP's are stable as long as the Cloud Service isn't deprovisioned; however, for maximum security, simplicity, and maintainability (i.e., even if a cloud service is deprovisioned), it would be awesome if we could have 301 redirects for the apex domain to a the www CNAME endpoint and not need to be concerned with the IP address of the Cloud Service at all. The scenario goes like…
1,371 votesWe are evaluating this feature ask. However, it is not on our immediate roadmap.
-Rohin K -
Azure Private DNS Zone resolution from OnPremise
Make it possible to enable the Name Resolution from onpremise if i have an azure private dns Zone.
It should be possible to make an Forward from onpremise dns to an azure private dns Zone.
1,193 votes -
Azure DNS query log
Hi,
I would like to request Azure DNS Query Log. This will help us identify traffic hitting record name in the dns zone.
Possible Log Sample
Time-Stamp,SourceIP,RecondType,RecordName
332 votes -
azure zones dns-forwarder
Please extend DNS zones solution to add forwarding & client features to implement the following in PaaS instead of with VMs:
https://github.com/Azure/azure-quickstart-templates/tree/master/301-dns-forwarderUse case: use azure dns to forward dns queries to 168.63.129.16 & between subnets. Enterprise DNS would forward to Azure DNS. VNET has Azure-provided name resolution (*.internal.cloudapp.net). In this way Enterprise DNS could dynamically learn of a PaaS offering on VNET.
331 votes -
Traffic Manager Private Endpoints
For Traffic Manager, allow us to use private endpoints (load-balancer) for fail over. It looks like someone created a work around using Web Apps but would like to have a supported method for RFC1918 addresses.
158 votes -
Traffic Manager- allow Internal routing option
Today Traffic Manager routes external traffic. For Azure PaaS (Web apps) ; deployed in Multiple regions ; if the applications are internal only; there is no option today to route the traffic to multiple ASE v2.0 (Internal)
112 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
Traffic Manager support blob storage
for web site availability, I would like to use blob storage under traffic manager when blob (such as pictures, pdfs , movies) is stored to blob storage.
91 votes -
Allow Traffic Manager to Support Absolute Monitoring Endpoints
Current endpoint monitoring in Traffic Manger only supports a relative path. For flexibility, it would be great to support a full url path like http://www.example.com/health
66 votesTraffic Manager constructs the probing URL by appending the endpoint FQDN with the relative path. So if the FQDN of your endpoint is example.com and a relative path is /index.html then the probing path would be example.com/index.html
You can also specify custom host header for each endpoint if required and set expected HTTP codes for the profile; in case the application does not return 200OK for the probes. Please see https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoringCould you elaborate on the scenario that would require absolute URLs for each endpoint?
-
Provide statistics to Azure DNS Services
Azure DNS Service has no statistics about requests, type of requests, origin of requests and so on ...
That can be useful to keep track of service costs and also to have a general view of our IaaS usage.63 votes -
designate set of name servers to all self hosted dns zones
When maintaining DNS Records in Azure, you have to update registrars records to use name servers assigned to a domain. Now that those nameserver sets varies, it takes extra effort to create Records, specially if you have to do it manually.
It would be easier if you could try and use same set of name servers to all dnz zones for the dns zones you are maintaining.58 votesThanks for the suggestion. We are tracking this on our backlog.
Some background: Azure DNS supports multiple name servers, which are dynamically assigned as zones are created. This allows us to let customers create zones without first proving that they own the domain name (since if we supported only a single name server set, we couldn’t allow just anyone to create a zone and thereby block the legitimate domain name owner). Domain proof-of-ownership checks are a significant hassle, so it’s important that we avoid them where possible.
Having said all that, I do understand that in some scenarios having a consistent set of name server names is desirable, and we are considering options for how we might support this in future.
-
Make Traffic manager able to access Web Apps that uses Authentication
Traffic manager is currently unable to get the status of a Web App that's using the Authentication/Authorization (simple auth) feature. It would be nice if it could use some kind of service account (or similar) to get authenticated and get the Web App status but still have the security features intact.
56 votes -
Support Azure Traffic Manager endpoints that are nested and external to allow us to use alias records
We have an Apex domain that needs to point to Traffic Manager. We use Traffic Manager nested profiles.
We want to use alias records to point to our DNS alias record to Traffic manager. This requires using external endpoints in traffic manager.
Problem is that we use nested profiles. It is not possible to create nested external endpoints in traffic manager.49 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
-
NAPTR Support (Name Authority Pointer)
Support NAPTR records with Azure DNS. These are primarily used to complement SRV records which you currently support.
https://en.wikipedia.org/wiki/NAPTR_record46 votesThank you for the feedback. We are tracking this ask on our backlog.
-
Integrate Windows IPAM with Azure DHCP
Integrate Windows IPAM with Azure DHCP services.
Some info can be gathered for domain members using DDNS, but not for appliances and other services not using DDNS...43 votesThank you for the feedback. We will consider this suggestion.
-
Formalize the Traffic Manager user agent string
I would like to see the user agent that Traffic Manager uses in its HTTP requests as part of monitoring/probing become formalized so that applications can take a dependency on the user agent string name and not worry about it changing in the future affecting the application that has behavior that depends on the user agent.
For an example where the user agent string is needed to comply with URL canonicalization needs along with Traffic Manager being involved, please refer to http://social.msdn.microsoft.com/Forums/azure/en-US/d9f8e779-644d-4263-990c-9de5a7cf403c/is-the-user-agent-for-traffic-manager-guaranteed.
41 votesWe included formalizing the Traffic Manager user agent string in our roadmap.
-
We need the new configuration in Azure Traffic Manager.
We need the new configuration in Azure Traffic Manager.
When prior region is replying intermittent healthy response to Traffice Manager, It occurs Failover and Failback repeatedly.
(e.g. In case the endpoint returns HTTP 500 intermittently by some system failure, if TM receives HTTP 200 by luck when TM probes there, TM sends requests to troublous endpoint until next probe chance.)We need the configuration that manual Failback.
39 votesThanks for the suggestion, we’ll consider how we can best support failover/failback during ‘grey’ failures in future, including a manual failback option.
-
Support Cisco Umbrella/OpenDNS SAML integeration
Add support for Cisco Umbrella/OpenDNS SAML integeration to Azure AD (existing open DNS enterprise app does not work)
36 votes
- Don't see your idea?