Skip to content

Comments

example: Use public DNS servers in VM network config#183

Merged
nirs merged 2 commits intomainfrom
default-dns-server
Feb 23, 2026
Merged

example: Use public DNS servers in VM network config#183
nirs merged 2 commits intomainfrom
default-dns-server

Conversation

@nirs
Copy link
Owner

@nirs nirs commented Feb 23, 2026

On managed Macs, corporate network extensions block DNS traffic from the vmnet bridge to the host's resolver (mDNSResponder), causing DNS lookups in the VM to fail. This also prevents installing avahi-daemon, breaking mDNS-based IP discovery.

Use 8.8.8.8 and 1.1.1.1 as static nameservers and disable DHCP-provided DNS, since the macOS host DNS cannot be trusted.

The dns servers can be changed using new --dns-server= option.

nirs and others added 2 commits February 23, 2026 04:26
On managed Macs, corporate network extensions block DNS traffic from
the vmnet bridge to the host's resolver (mDNSResponder), causing DNS
lookups in the VM to fail. This also prevents installing avahi-daemon,
breaking mDNS-based IP discovery.

Use 8.8.8.8 and 1.1.1.1 as static nameservers and disable DHCP-provided
DNS, since the macOS host DNS cannot be trusted.

Co-authored-by: Cursor <cursoragent@cursor.com>
Allow overriding the default DNS servers (8.8.8.8, 1.1.1.1) for users
who prefer private DNS servers or have specific company policies.

Example:

    % ./example test --dns-servers 10.0.0.1,10.0.0.2
@nirs nirs added this to the v.0.10.0 milestone Feb 23, 2026
@nirs nirs merged commit b1fa348 into main Feb 23, 2026
12 checks passed
@nirs nirs deleted the default-dns-server branch February 23, 2026 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant