---
title: Azure – You can now use FQDN name to define your Local Network Gateway - cubesys
description: As you know, you can setup a Site-to-Site VPN between your on-premises infrastructure and Azure.This VPN connectivity involves the creation of a Local Network Gateway (LNG).Until now, you add to configure a public IP for your LNG.Well, good news you can now use a Fully Qualified Domain Name (FQDN) instead…
---

[Latest News & Blogs - cubesys ](https://www.cubesys.com.au/blog)

# [Azure – You can now use FQDN name to define your Local Network Gateway - cubesys](https://www.cubesys.com.au/blog/azure-you-can-now-use-fqdn-name-to-define-your-local-network-gateway)

 Written by [cubesys](https://www.cubesys.com.au/blog/author/cubesys) | Oct 21, 2020 1:00:00 PM

As you know, you can setup a Site-to-Site VPN between your on-premises infrastructure and Azure.

This VPN connectivity involves the creation of a Local Network Gateway (LNG).

Until now, you add to configure a public IP for your LNG.

Well, good news you can now use a Fully Qualified Domain Name (FQDN) instead of the public IP. This is quite handy if you have to connect branch offices which may use a dynamic public IP.

To start using this new capability, logon to your Azure portal ([https://portal.azure.com](https://portal.azure.com/)) and create a new LNG

<https://www.cubesys.com.au/hubfs/Imported_Blog_Media/image_thumb-346.png>

Then you can switch to **FQDN** for the endpoint definition

<https://www.cubesys.com.au/hubfs/Imported_Blog_Media/image_thumb1-274.png>  <https://www.cubesys.com.au/hubfs/Imported_Blog_Media/image_thumb2-212.png>

**NOTES**

- Only 1 public IP is support when using FQDN. If the FQDN resolves to multiple IP’s, Azure VPN will then use the first IP returned.
- Azure VPN is caching DNS resolution for 5 minutes, which may lead to temporary disconnection when the public IP is updated
- The gateway tries to resolve FQDN only for disconnected tunnels (or if you reset the gateway)

[View full post](https://www.cubesys.com.au/blog/azure-you-can-now-use-fqdn-name-to-define-your-local-network-gateway)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "cubesys"
  },
  "dateModified" : "2025-02-21T16:26:35.095Z",
  "datePublished" : "2020-10-21T13:00:00Z",
  "headline" : "Azure – You can now use FQDN name to define your Local Network Gateway",
  "image" : {
    "@type" : "ImageObject",
    "height" : 60,
    "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
    "width" : 60
  },
  "mainEntityOfPage" : "https://www.cubesys.com.au/blog/azure-you-can-now-use-fqdn-name-to-define-your-local-network-gateway",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "Latest News"
  }
}
```