Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Configured DNS servers not used after client update to 2.1.1 on macOS

Open
#1,175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
cli, networking

Research direction

Look at the DNS configuration logic in the macOS client, likely in a network configuration module. Start by checking how DNS servers are applied after an update from version 1.6.9 to 2.1.1. Reproduce the issue by simulating an update and connection, then verify the DNS settings are not being set automatically. 'Done' is when the client uses configured DNS servers without manual intervention.

Written by the indexing model from the issue text.

Description

bug
Summary

We have added 2 DNS servers and 1 domain at the location. Everything works with 1.6.9 clients. One Mac user (macOS 27, Golden Gate) had the client (installed from the App Store) updated automatically from 1.6.9 to 2.1.1.
After the initial connection, the configured DNS servers are not used, which causes problems when trying to reach internal sites. Only after manually adding the DNS servers does everything work as expected.

Steps to reproduce
  1. Update the client from a working 1.6.9 to 2.1.1
  2. Connect to a location where DNS servers are configured
  3. Try to reach sites that require the internal DNS servers
  4. After it fails, add the DNS servers manually and repeat step 3
  5. Now it works
Expected behavior

The VPN uses the configured DNS servers automatically when connected.

Actual behavior

The internal DNS servers are not used for DNS resolution.

Defguard version

Core: 2.0.0-beta1, Gateway: 2.0.0-beta1 (OPNsense), Edge: 2.0.0-beta1, Desktop Client: 2.1.1

Environment details

macOS 27

Deployment / install method

Docker / Docker Compose

Relevant logs / output
Relevant configuration (redacted)
Dominant language
Rust
Stars
370
Forks
39
Avg merge
20h 1m
Merged PRs (30d)
37

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DefGuard/client

All issues in DefGuard/client

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.