Reverse Proxy function not working when using ipv4 and ipv6 dual stack setup with clients

I’ve been previously running an ipv4 setup and have recently enhanced this with ipv6 using SLAAC. I have a reverse proxy configuration that allows me to redirect web requests to a local ip address/port. This runs well with ipv4 only, however as soon as a client also receives an ipv6 address this service does not work anymore.

My ipv4 configuration contains the following specifics for the reverse proxy function:

set service dns forwarding authoritative-domain xx.local records a paperless address ‘xxx.xxx.0.1’
set service dns forwarding listen-address ‘xxx.xxx.0.1’
set load-balancing reverse-proxy service http description ‘bind app listen on 80 port’
set load-balancing reverse-proxy service http mode ‘tcp’
set load-balancing reverse-proxy service http port ‘80’
set load-balancing reverse-proxy service http rule 1 domain-name xx.local
set load-balancing reverse-proxy service http rule 1 set backend ‘bk-api-01’
set load-balancing reverse-proxy backend bk-api-01 description ‘My API-1’
set load-balancing reverse-proxy backend bk-api-01 mode ‘tcp’
set load-balancing reverse-proxy backend bk-api-01 server api01 address ‘xxx.xxx.0.2’
set load-balancing reverse-proxy backend bk-api-01 server api01 port ‘8777’

Maybe client performs a DNS request using IPv6 to public server, bypassing your DNSforwarder

Many thanks for your reply, managed to resolve the problem. Mac OS does prioritize the ipv6 dns over ipv4.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.