Please extend DNS zones solution to add forwarding & client features to implement the following in PaaS instead of with VMs:
Use case: use azure dns to forward dns queries to 184.108.40.206 & 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.92 votes
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.53 votes
allow creating of private zone for non-empty vnet.46 votes
Thank you for the feedback. This is planned for when we go GA (coming soon !)
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 votes
We included formalizing the Traffic Manager user agent string in our roadmap.
Thank you for supporting CAA records via CLI/PowerShell/API - but for the majority of people, this isn't easy. Please add support for these records in the DNS zone management blade.22 votes
This is on our plan. Thanks for your feedback !
I'm surprised to learn the Traffic Manager does not support the client-subnet feature. Most major CDNs & DNS providers seem to support it.19 votes
When using the Alias Record Set of Azure DNS, it becomes an error if it is a domain name.
App Service has a VIP, I would like an option to add IP instead of domain name.10 votes
Thank you for your feedback. We are working on supporting more Traffic Manager endpoint types to work with ALIAS record type.
when adding endpoints to the traffic manager, you get all app-services that are available, but in our case, the list is very long, and searching makes it difficult. The list is not sorted, and neither can we filter it.
Adding a filter would be very helpfull.4 votes
Currently Azure DNS Zone will randomly create Zone records in different DNS Servers.
I have a public DNS server which I would like to migrate to Azure DNS Zone, to do this I need maintain my name servers but redirect to Azure's. because every time I create a new zone it is generated in a different DNS Server I can't create the CNAMEs to easily migrate my clients domains.
Could this feature be added.3 votes
Thank you for the feedback. If you are referring to DNS zone transfer, this has been included in our current planning cycle.
We have several app-ways in the same subnet.
Traffic analytics is display a DestIP_s which does not correspond with the displayed NIC_s (it belongs to a different app-way).1 vote
Is adding external endpoints via IP address available instead of FQDN? i don't think it is? can some one clarify it please..
On Azure Traffic Manager, is external endpoints addition via IP address available instead of FQDN? i don't think it is yet? can some one clarify it please..1 vote
- Don't see your idea?