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.
2,911 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.
916 votesThis remains on our long-term backlog as something we want to offer as part of the Azure DNS service in due course. Thank you everyone for the feedback so far, and please continue to share your comments.
-
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.
858 votesThanks you for the suggestion. This remains a key backlog item for us.
We’d be interested in further input via your comments. Please consider the following questions:
– Do you require zone transfers in to Azure DNS, or zone transfers out? Why?
– Do you require AXFR or IXFR?
– How should zone transfers be secured? -
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…
529 votesWe’re tracking this on our long-term backlog. However, it’s unlikely that we’ll support this in the near future.
Thank you for the suggestion and please keep the votes and ideas coming.
-
Traffic Manager Failover profile alert
Can you please add alert rule for Azure traffic manager to update the co-admin by sending mail alert whenever there is a down of primary / secondary and switch over?
Since our customer wants to create alert for this scenario.
This will greatly relax the customer to sit in a place to watch service changes through mail.
322 votes -
Possibility to set a DNS Suffix on Azure networks (like DNS Servers)
There are many scenarios for Virtual Machines (and Other maybe) where NIC settings are cleared (VM Deallocated). DNS Servers can be set on Azure Network, and this VM will have DNS Servers settings via DHCP. But we have to set DNS Suffix manually each time, or set a script automatically at each boot.
The idea is just to have a way to set a suffix DNS for VM Networks, with the same way as DNS Servers. With this settings, DHCP will assign DNS suffix to all VM automatically.280 votesThis remains a high-pri item on our feature backlog.
-
Introduce 'Vanity name servers'
We would like to see an introduction of delegations using name server names in our own zone (sometimes called 'vanity name servers').
Using 'vanity name servers' are important for consolidating our corporate brand.
Currently, the 'host' field of the SOA and the NS records at the zone apex are deliberately locked to discourage us from setting up delegations other than via the Azure DNS name server names.
We realise such delegations would break were we ever to change the Azure DNS name server IP ranges in future, which would obviously need to be resolved prior to the introduction of this.
…
177 votesGood feedback. We’re tracking this as a backlog item, but please note it’s likely to be quite far out. Please keep your votes coming!
-
Enable split DNS for providing both public and internal name resolution to VMs in the VNET.
Amazon Route 53 supports split-view DNS, so you can configure public and "PRIVATE" hosted zones to return different external and internal IP addresses for the same domain names.
i think a similar capability can be very useful also in Azure143 votesWe just announced public preview for Azure DNS Private Zones, which supports split-horizon scenarios.
https://docs.microsoft.com/en-us/azure/dns/private-dns-overview
-
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
125 votes -
Traffic Manager Logging & Alerts
Traffic Manager needs to keep track of past endpoint health failures.
In addition to this it should be possible to configure alerts about changes to endpoint health.107 votes -
Support HTTP redirect records in Azure DNS
Please make Azure DNS support HTTP redirect records. http://www.domain.com -> http://www.domain2.com/sub/index.htm
93 votes -
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.
86 votes -
Introduce CNAME flattening
Does
#Azure
#DNS
support CNAME flattening #CloudFlare
style? The answer is no yet it would be a very handy feature.See here for more details on how CloudFlare is doing it, and they might actually have introduced the whole notion of "CNAME flattening": https://support.cloudflare.com/hc/en-us/articles/200169056-CNAME-Flattening-RFC-compliant-support-for-CNAME-at-the-root
85 votes -
Add more configurability to Traffic Manager monitoring endpoint
I would like for the monitoring endpoint configuration to support two new options:
1) How many consecutive times TrafficMgr does not get an http 200 from the endpoint before it deems it down. I have a scenario where I want it to be deemed down immediately after one failure for a quicker failover.
2) How many consecutive times TrafficMgr receives an http 200 after it has deemed it down before it will deem it up again. I have seen a scenario where table storage (or SQL Azure) is inconsistent (fails one query then succeeds the next, back and forth) and…79 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.
68 votesvalid suggestion subject to customer upvote
-
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
63 votes -
Create private dns zone in virtual network which already has VMs
Create private dns zone in virtual network which already has VMs. Currently, it's giving below error:
`Virtual networks that are non-empty (have Virtual Machines or other resources) are not allowed during association with a private zone.`
60 votesWe are working on this and it should be available on or before GA of the service.
-
Add DNS name label to private IPs
Currently when using Azure provided DNS all VM's are registered automatically using VM name. Unfortunately it's not possible to register other resources like for example load-balancers with private IPs. It would be great to be able to assign dns name to private IPs
55 votesAzure DNS Private Zones is in Public Preview, which supports split-horizon scenarios.
https://docs.microsoft.com/en-us/azure/dns/private-dns-overviewWe will support non-empty Vnets very soon. Stay tuned !
-
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.48 votes -
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.
45 votes
- Don't see your idea?