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
Azure DNS Private Zones is in Public Preview, which supports split-horizon scenarios.
We will support non-empty Vnets very soon. Stay tuned !
How soon is "We will support non-empty Vnets very soon. Stay tuned !"?? Your history suggests "soon" might equate to years!!!
Private DNS Zones is almost useless until this can be turned on for VNets wich are not empty. Even being able to target a particular subnet would help, as it's fairly easy to move between subnets, unlike VNets.
Hello, we are working on supporting existing (non-empty) VNETs. This is coming very soon ! Stay tuned.
+1 to Glen Little's comment below! I'm trying to use Hybrid Connection with Service Fabric and since it's not recommended to use ILB's IP address with it I don't really have any other options. Please make this happen.
Glen Little commented
Private Zones look good, but currently, they cannot be added to an existing (production) VNET. Please make this possible! (Don't need the auto registration, just need to manually add local DNS entries for existing VMs.)
Hi can I update DNS name label of private IP.
Does this also mean there will be an internal DNS service? I would like the ability to use the equivalent of Azure Traffic Manager, but internally. e.g. I have applications hard coded to an internal DNS entry protocol.domainname.xyz that is not resolvable on the internet, and have traffic redirected to internal VIP2 if the machines behind the internal VIP1 all go offline. The A record of the internal DNS name gets updated if the health probe fails VIP1.