Jamil 6fc7d2e4e0 feat(portal): configurable ip stack for DNS resources (#9303) ...

Some poorly-behaved applications (e.g. mongo) will fail to connect if
they see both IPv4 and IPv6 addresses for a DNS resource, because they
will try to connect to both of them and fail the whole connection setup
if either one is not routable.

To fix this, we need to introduce a knob to allow admins to restrict DNS
resources to only A or AAAA records.


<img width="750" alt="Screenshot 2025-06-02 at 10 48 39 AM"
src="https://github.com/user-attachments/assets/4dbcb6ae-685f-43ee-b9e8-1502b365a294"
/>

<img width="1174" alt="Screenshot 2025-06-02 at 11 05 53 AM"
src="https://github.com/user-attachments/assets/02d0a4b3-e6e8-4b6d-89fa-d3d999b5811e"
/>

---

Related:
https://firezonehq.slack.com/archives/C08KPQKJZKM/p1746720923535349
Related: #9300
Fixes: #9042

2025-06-03 02:24:41 +00:00

..

web

feat(portal): configurable ip stack for DNS resources (#9303)

2025-06-03 02:24:41 +00:00

web.ex

chore(portal): Bump all deps related to portal (#6445)

2024-08-28 10:40:02 -06:00