[Bug]: Configured DNS servers not used after client update to 2.1.1 on macOS
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 65/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- macos, rust
- Área
- cli, networking
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Update the client from a working 1.6.9 to 2.1.1
- Connect to a location where DNS servers are configured
- Try to reach sites that require the internal DNS servers
- After it fails, add the DNS servers manually and repeat step 3
- 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)
- Lenguaje dominante
- Rust
- Estrellas
- 370
- Forks
- 39
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 37
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DefGuard/client
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
bug
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
-
Handle corrupt app database Abiertodesign
Todos los issues de DefGuard/client
Issues similares
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yantrikos/yantrik-os#255 ·
-
Replayed reasoning items send "content": null, which the Responses API schema does not permit Abiertobug CLI custom-model
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
raphamorim/rio#1956 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comentario ·