DNS IP address changes after stopping and starting Advanced Threat Defense using the Azure Portal

Technical Articles ID: KB90718
Last Modified: 2022-10-06 09:01:00 Etc/GMT

Environment

Advanced Threat Defense (ATD)
Intelligent Sandbox (IS)
Microsoft Azure

Problem

Manually configured DNS IP addresses aren't retained after you perform a stop and start of virtual ATD/IS (vATD/vIS) using the Azure Portal.

Cause

vATD/vIS on the Azure Portal obtains the IP address details (IP address, netmask, DNS, and gateway) from a DHCP Server.

Solution 1

Configure the needed DNS server using the Azure Portal.

IMPORTANT: After you configure the DNS server using the Azure Portal, perform a system restart to allow the DNS settings to take effect.

To set up a custom DNS in the Azure Portal, perform the steps below:

Access Virtual-networks, DNS Server.
Select Custom DNS.
Configure your custom DNS Server.
Save the changes.
Restart the system.

The custom DNS is now automatically assigned to the vATD/vIS every time it stops and starts.

Solution 2

Configure the needed DNS server manually after each stop and start of vATD/vIS.

To set up the DNS server manually for vATD/vIS:

Access the vATD/vIS user interface.
Navigate to the Manage, ATD Configuration, DNS page.
Configure the needed DNS server details under the DNS Settings section.
Save the settings, and then click Apply.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

DNS IP address changes after stopping and starting Advanced Threat Defense using the Azure Portal

Environment

Problem

Cause

Solution 1

Solution 2

Affected Products

Languages:

Title

Title

Knowledge Center

DNS IP address changes after stopping and starting Advanced Threat Defense using the Azure Portal

Environment

Problem

Cause

Solution 1

Solution 2

Affected Products

Languages:

Choose your region

Title

Title