[Bug]: DNS Resolution Fails in Guest VM After Upgrading to VirtualBox 7.2.4 on Ubuntu 22.04 Host

[EvgeniyRub]

Version

7.2.4

Host OS Type

Linux

Host OS name + version

Ubuntu 22.04 LTS

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Other Linux (64-bit)

Component

Network

What happened?

VirtualBox: NAT network 10.0.0.0/24 , SSH port forwarding configured
DNS resolution stops working within the guest which has static IP from current IP ranges.
It works as it was before update for guests as DHCP-clients.

guest ip 10.0.0.100

resolv.conf file content:

nameserver 10.0.0.100
nameserver 10.0.0.1
search .

NAT Networks:

Name:         aos-network-aos-test-s1
Enabled:      Yes
Network:      10.0.0.0/24
Gateway:      10.0.0.1
DHCP Server:  Yes
IPv6:         No
IPv6 Prefix:  fd17:625c:f037:2::/64
IPv6 Default: No
Port-forwarding (ipv4)
        mainssh:tcp:[]:8737:[10.0.0.100]:22
loopback mappings (ipv4)
        127.0.0.1=2

1 network found

NetworkName:    aos-network-aos-test-s1
Dhcpd IP:       10.0.0.2
LowerIPAddress: 10.0.0.3
UpperIPAddress: 10.0.0.254
NetworkMask:    255.255.255.0
Enabled:        Yes
Global Configuration:
    minLeaseTime:     default
    defaultLeaseTime: 86400 sec
    maxLeaseTime:     default
    Forced options:   None
    Suppressed opts.: None
        1/legacy: 255.255.255.0
        3/legacy: 10.0.0.1
        6/legacy: 1.1.1.1
       15/legacy: privatelink.azurecr.io
Groups:               None
Individual Configs:   None

It works for 7.1.4 but doesn't for 7.2.4 Looks like some kind of regression occurs.

It is not suitable configure DNS on guest itself.

Before update (7.1.14):

resolvectl status
Global
           Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: uplink
         DNS Servers: 10.0.0.100
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 8.8.8.8#dns.google 1.0.0.1#cloudflare-dns.com 8.8.4.4#dns.google 2606:4700:4700::1111#cloudflare-dns.com
                      2001:4860:4860::8888#dns.google 2606:4700:4700::1001#cloudflare-dns.com 2001:4860:4860::8844#dns.google

Link 2 (enp0s3)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
       DNS Servers: 10.0.0.1

Link 3 (sit0)
    Current Scopes: none
         Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
root@main:~# ping google.com
PING google.com (142.251.140.14): 56 data bytes
64 bytes from 142.251.140.14: seq=0 ttl=116 time=12.883 ms
64 bytes from 142.251.140.14: seq=1 ttl=116 time=11.672 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 11.672/12.277/12.883 ms

After update (7.2.4):

resolvectl status
Global
           Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: uplink
  Current DNS Server: 10.0.0.100
         DNS Servers: 10.0.0.100
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 8.8.8.8#dns.google 1.0.0.1#cloudflare-dns.com 8.8.4.4#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2001:4860:4860::8888#dns.google
                      2606:4700:4700::1001#cloudflare-dns.com 2001:4860:4860::8844#dns.google

Link 2 (enp0s3)
    Current Scopes: DNS
         Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.0.0.1
       DNS Servers: 10.0.0.1

Link 3 (sit0)
    Current Scopes: none
         Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
root@main:~# ping google.com
ping: bad address 'google.com'

How can we reproduce this?

1. Deploy linux OS guest
2. Configure NAT network network connection ( DHCP Enable)
3. Check DNS resolution from the quest

Logs provided in attachments

VBox_7_1_14.log
VBox_7_2_4.log

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.