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:

  • Service overview

  • Technical documentation

  • Pricing details
  • Traffic Manager:

  • Service overview

  • Technical documentation

  • Pricing details
  • Network Watcher:

  • Service overview

  • Technical documentation

  • Pricing details
  • If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.

    • Hot ideas
    • Top ideas
    • New ideas
    • My feedback
    1. 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-forwarder

      Use 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.

      87 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    2. 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.

      53 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  3 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    3. Microsoft could be a provider of domain registrations.

      Currently we use Registro.br, Godaddy, 101Domain, Amazon Route 53, Google Domains among others for domain registrations. Microsoft could be a provider of domain registrations. It would be another service that would add to the cloud services already offered by Microsoft. Having everything centralized would be ideal, all in one invoice and customer loyalty.

      20 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    4. 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)

      20 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    5. Allow Private DNS zones to have IP address from a vNet assigned rather than use Azure DNS Its

      This would allow for on-prem resolution for Private DNS. This would avoid having to stand up DNS proxy servers in each vNet all pointing to the same IP address

      6 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    6. 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.

      4 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    7. add source port for every conversation in Traffic Analytics dashboard

      Currently sessions are summarized for source IP to desination IP+port. There is source port missing in that schema which would allow for recognition of separate conversations to the same client+service pair.

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    8. show destination public IPs in Traffic Analytics

      Currently, there is summarization done for destination public IPs and only destination region is visible in Traffic Analytics. Sessions to different public IPs are not separated in the dashboard, hence summary outgoing volume can be viewed only.

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    9. Adding a Website subdirectory as part of the CNAME

      Creating a CNAME should allow us to point to a Sub Directory for an existing Website.
      For example: I can add a CNAME for a website like www.xyz.com
      But I should also be allowed to point it to the a subdirectory within the Website like www.xyz.com/abc/

      This will help simplify the task and reduce the operational hindrance of using Application Gateways along with DNS CNAME

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    10. Azure DNS Logs

      Need to access DNS Request Logs on "Azure DNS" service. Actually, we can't search on any logs if we get a DDOS attack on our zone. So, we can receive a big invoice because of huge query number without to know who is requesting our DNS zone.

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    11. Offer a domain registry service to go along with Azure DNS

      Very simple convenience feature - when everything else is handled on Azure, why make me involve a third party just for the domain registration?

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    12. Support SSHFP records in Azure DNS zones

      Since Windows now supports OpenSSH natively, as well as Linux and other clients/servers on the same network, supporting this standard for server authentication seems like an obvious win.

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    13. Tags for DNS Record - with space in Tagname

      Public DNS Records currently don't allow Tagnames containing space character - we checkt this in support case 119072222001569. As far as we know all other Provider do support this. Please add this to DNS Record as well so that we have the same Tagging cababilities with all Resource Providers.

      2 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    14. Support LOC records in Azure public DNS zones

      LOC records provide geographical information useful for planning, debugging, etc. Ideally, such support would include both custom LOC records for on-premises domains, subdomains, and hosts, and the option of using a LOC record matching the Azure location of a given public IP.

      2 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    15. Allow increase of DNS alias quota

      Currently there is a hard limit of 20 DNS alias records per public IP. This quote is not documented anywhere, nor is it able to be changed by any support staff.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    16. DNSSEC support on Azure DNS servers

      DNSSEC support on Azure DNS servers

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    17. DNS Services

      Hello Support,
      we request you if there DNS Services we can use for our internal AD instead of using DNS of ISP or any other third party like Google or OpenDNS to lookup, is there anything similar to this not Azure AD services.

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
    18. Allow single top level domain for private zone name

      Allow to create private DNS zone like .lan. Currently zone names require 2 or more labels (foo.lan).

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks 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

    • Don't see your idea?

    Feedback and Knowledge Base