Thomas Eizinger cd650de1f8 refactor: prepare client init for upstream DoH servers (#10851) ...

In order to support multiple different protocols of upstream DNS
resolvers, we deprecate the `upstream_dns` field in the client's `init`
message and introduce two new fields:

- `upstream_do53`
- `upstream_doh`

For now, only `upstream_do53` is populated and `upstream_doh` is always
empty.

On the client-side, we for now only introduce the `upstream_do53` field
but fall-back to `upstream_dns` if that one is empty. This makes this PR
backwards-compatible with the portal version that is currently deployed
in production. Thus, this PR can be merged even prior to deploying the
portal.

Internally, we prepare connlib's abstractions to deal with different
kinds of upstreams by renaming all existing "upstream DNS" references to
`upstream_do53`: DNS over port 53. That includes UDP as well as TCP DNS
resolution.

Resolves: #10791

---------

Co-authored-by: Jamil Bou Kheir <jamilbk@users.noreply.github.com>

2025-11-12 05:40:58 +00:00

..

api

refactor: prepare client init for upstream DoH servers (#10851)

2025-11-12 05:40:58 +00:00

api.ex

feat(portal): Filtering, Fulltext Search, Pagination, Preloads (#3751)

2024-03-16 13:27:48 -06:00