<p>There is <a href="https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services" rel="nofollow noreferrer">another manual</a> for enabling reverse lookup DNS in azure.</p>
<blockquote>
<p><strong>Will my reverse DNS records resolve from the internet?</strong></p>
<p>Yes. Once you set the reverse DNS property for your Azure service,
Azure manages all the DNS delegations and DNS zones required to ensure
that reverse DNS record resolves for all Internet users.</p>
<p><strong>Are default reverse DNS records created for my Azure services?</strong></p>
<p>No. Reverse DNS is an opt-in feature. No default reverse DNS records
are created if you choose not to configure them.</p>
</blockquote>
<p>It seems that reverse dns has to be enabled if it is used internally.</p>

CC BY-SA 3.0
2017-11-26T11:44:56.767Z
2017-11-26T11:44:56.767Z
2020-06-18T08:28:10.803Z
030
<p>I have a <code>Virtual network</code> (MyVPN) resource in Azure, being a class C network, MyVPN has <code>Azure provided DNS service</code> as DNS servers, so all virtual machines with a NIC connected to this network are able to resolve their hostname successfully, for example virtual machine <code>myvm01</code> can ssh to <code>myvm02</code> using only the hostname instead of IP.</p>

<p>However, they are unable to make a reverse DNS lookup, which makes sense since by default Azure does not provide a <code>reverse DNS lookup zone</code>. <a href="https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-hosting" rel="nofollow noreferrer">By following Microsoft's documentation</a> I managed to create it, sadly I don't really know if I should delegate to <code>Azure provided DNS service</code> and if so, how to do it (I tried <a href="https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns" rel="nofollow noreferrer">following this</a>)</p>

<p>What should I do now to allow <code>myvm01</code> be able to resolve the IP of <code>myvm02</code> to its hostname?</p>

<azure><dns>
Azure and DNS services
Navarro
# Azure and DNS services

(Asked by: username_0 on 2017-07-13)

I have a `Virtual network` (MyVPN) resource in Azure, being a class C network, MyVPN has `Azure provided DNS service` as DNS servers, so all virtual machines with a NIC connected to this network are able to resolve their hostname successfully, for example virtual machine `myvm01` can ssh to `myvm02` using only the hostname instead of IP.

However, they are unable to make a reverse DNS lookup, which makes sense since by default Azure does not provide a `reverse DNS lookup zone`. [By following Microsoft's documentation](https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-hosting) I managed to create it, sadly I don't really know if I should delegate to `Azure provided DNS service` and if so, how to do it (I tried [following this](https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns))

What should I do now to allow `myvm01` be able to resolve the IP of `myvm02` to its hostname?

**Tags:** azure, dns


---

## 1 answers

### Answer by username_1 on 2017-11-26. Score: 1

There is [another manual](https://docs.microsoft.com/en-us/azure/dns/dns-reverse-dns-for-azure-services) for enabling reverse lookup DNS in azure.

> **Will my reverse DNS records resolve from the internet?**
>
> Yes. Once you set the reverse DNS property for your Azure service,
> Azure manages all the DNS delegations and DNS zones required to ensure
> that reverse DNS record resolves for all Internet users.
>
> **Are default reverse DNS records created for my Azure services?**
>
> No. Reverse DNS is an opt-in feature. No default reverse DNS records
> are created if you choose not to configure them.

It seems that reverse dns has to be enabled if it is used internally.


---

