fix: Update DNS widget to use A record pointing to Approximated proxy IP #636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixed DNS widget configuration to correctly route through Approximated proxy using an A record instead of CNAME.
Problem
The DNS widget was instructing clients to:
sales-agent.scope3.comSolution
Updated DNS widget to:
37.16.24.200(Approximated proxy cluster IP)Architecture Flow
Changes
src/admin/blueprints/settings.py): Returnproxy_ipinstead ofdns_targettemplates/tenant_settings.html): Use A record type with proxy IPdocker-compose.yml): AddAPPROXIMATED_PROXY_IPenv var (default: 37.16.24.200)CLAUDE.md): Update configuration documentationTesting
Screenshots
See attached images showing:
sales-agent.scope3.com🤖 Generated with Claude Code