Reasoning of disabling of the first nat interface/adapter 1

[Cergical]

I saw in the domain-controller-configuration script that you have disabled the physical nat-adapter of the virtual machine. It was specified in the comments that the reason why it is removed is to prevent the interface from being registered in the DNS server. For convenience, I have copied and pasted the portion of the script verbatim below:

# remove the non-routable vagrant nat ip address from dns.
# NB this is needed to prevent the non-routable ip address from
#    being registered in the dns server.
# NB the nat interface is the first dhcp interface of the machine.
$vagrantNatAdapter = Get-NetAdapter -Physical `
    | Where-Object {$_ | Get-NetIPAddress | Where-Object {$_.PrefixOrigin -eq 'Dhcp'}} `
    | Sort-Object -Property Name `
    | Select-Object -First 1
$vagrantNatIpAddress = ($vagrantNatAdapter | Get-NetIPAddress).IPv4Address
# remove the $domain nat ip address resource records from dns.
$vagrantNatAdapter | Set-DnsClient -RegisterThisConnectionsAddress $false
Get-DnsServerResourceRecord -ZoneName $domain -Type 1 `
    | Where-Object {$_.RecordData.IPv4Address -eq $vagrantNatIpAddress} `
    | Remove-DnsServerResourceRecord -ZoneName $domain -Force
# disable ipv6.
$vagrantNatAdapter | Disable-NetAdapterBinding -ComponentID ms_tcpip6
# remove the dc.$domain nat ip address resource record from dns.
$dnsServerSettings = Get-DnsServerSetting -All
$dnsServerSettings.ListeningIPAddress = @(
        $dnsServerSettings.ListeningIPAddress `
            | Where-Object {$_ -ne $vagrantNatIpAddress}
    )
Set-DnsServerSetting $dnsServerSettings
# flush the dns client cache.
Clear-DnsClientCache

My question is, what are the side effects, if any, of not disabling the first DHCP interface on the domain's operations, and why is it necessary to prevent the interface from being registered on the DNS?. Since I am creating a virtual Active Directory home lab environment, it didn't occur to me that the interface should be disabled. This could be due to a lack of knowledge in developing a vagrant environment and AD. Would highly appreciate your insights here.

[rgl]

its just to prevent the windows domain clients from ever seeing the vagrant management ip address advertised as a dc ip address. because, in this particular vagrant environment, they will not be able to connect to that ip address.