I had a non openwrt router till a month back with IPv4 only network. And my work pc was connecting to work using company configured zscaler fine.
A month back I had changed to openwrt 24.10.4 and which also enabled IPv6 (When I do https://whatismyipaddress.com/, I get both IPv4 and IPv6 address).
Everything works on personal devices, which includes wireguard VPNs to other sites etc.
But my work pc not able to connect to office network using zscaler.
Could this be a openwrt router configuration or ISP side issue thats casuing this?
Something more to add,
same laptop instead of this home router, if I use mobile hot spot, everything works.
same laptop instead of this home router, if I use my another city another home, another ISP openwrt router, everything works.
But what do you see locally, on your router?
I guess you have public (GUA) IPv6 on wan6 but what address do you see on your wan? You don't need to hide the address if it belongs to private address space.
What's the result of nslookup gateway.zscaler.net on the client PC?
nslookup gateway.zscaler.net
DNS request timed out
timeout was 2 seconds.
Server: Unknown
Address: 192.168.1.1
DNS request timed oit
timeout was 2 seconds.
DNS request timed oit
timeout was 2 seconds.
DNS request timed oit
timeout was 2 seconds.
DNS request timed oit
timeout was 2 seconds.
*** Request to Uknown timed-out
When client pc is connected to mobile hotspot,
nslookup gateway.zscaler.net
Server: Unknown
Address: 127.0.0.1
Dns reqeust timed out
timeout was 2 seconds.
Non-authorititave answer:
Name: gateway.zscaler.net
Address: 165.2xx.xxx.14
This is not the case, look into nslookup output you provided.
You can direct the DNS request on the 2nd PC to another IP by running nslookup gateway.zscaler.net 192.168.1.1
from the second pc, which is connected to same home network, now its not resolving when I used 192.168.1.1
C:\Users\sim_t>nslookup gateway.zscaler.net 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
C:\Users\sim_t>
So it got 192.168.1.1 and fd12:e137:9401::1 and it is with fd12:e137:9401::1 it earlier used to resolve.
Infact nothing at home network resolve using 192.168.1.1
C:\Users\sim_t>nslookup google.com 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
That's a good point, I forgot about this. At the same time I would expect name resolution working before Zscaler is up and running. BTW, I do not see a timeout myself, it's some dummy response.
@lleachii@AndrewZ
Yes. my second Location/ISP got IPv6 too.
There I could correctly resolve google.com as well gateway.zscaler.net using 192.168.0.2 (which is my openwrt router address at second Location)
In the current site where I have this problem DNS is not working with any website using 192.168.1.1 (which is my current site openwrt router address).
What troubleshooting approach I can take to solve it?
Basically in the problem site dns resolution works only with ipv6 (Server: OpenWrtTcr.lan ,Address: fd12:e137:9401::1) and not with 192.168.1.1. And my workpc got only IPv4.