NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR1000 v1 DNS not working when VPN is enabled
I've XR1000 v1 router with the following settings:
- firmware: 1.0.2.86_2.1.40
- IP address: 192.168.2.1
and DNS stops working as soon as I enable VPN on it (see nslookup output below).
Resetting the router didn't help.
Setting primary/secondary DNS servers manually to 8.8.8.8, 1.1.1.1, etc. on the router didn't help.
Please advice.
With VPN enabled:
$ nslookup www.google.com 192.168.2.1
;; communications error to 192.168.2.1#53: connection refused
;; communications error to 192.168.2.1#53: connection refused
;; communications error to 192.168.2.1#53: connection refused
;; no servers could be reached
With VPN disabled:
$ nslookup www.google.com 192.168.2.1
Server: 192.168.2.1
Address: 192.168.2.1#53
Non-authoritative answer:
Name: www.google.com
Address: 142.251.154.119
. . .
12 Replies
Thanks for pointing out that the nslookup command has a feature to define the DNS server. (best thing about the Forum is "learning new things every day")
Same thing happens when the command is only nslookup www.google.com?
Other attempts to resolve URLs also fail?
(such as opening web pages?)
I seem to recall someone else having this issue and from memory there wasn't a solution and it's very unlikely NTGR will resolve this now. FURRYe38 was it you that had this issue?
To clarify: DNS queries are failing on the LAN clients, not on VPN clients (didn't test DNS on VPN clients at all).
Scenario is simple: LAN client sends DHCP request to the router and receives back an IP address, e.g. 192.168.2.123, and DNS server 192.168.2.1 (address of the router).
When VPN is off: LAN client uses 192.168.2.1 DNS server to resolve the addresses and receives DNS responses from the router.
When VPN is on: the same LAN client, sends the same DNS queries to the same 192.168.2.1 DNS server - no responses from the router.
Looks like firmware bug for me.
What LAN IP address are you using? Default 192.168.1.1 or something different? Looks like your using 192.168.2.1?
What brand and model# ISP modem or ONT is the router connected too?
How is VPN setup on the router? I presume your using the built in VPN feature?
What happens if you use ISP detected DNS with VPN disabled and enabled?
Right now, I'm using 192.168.2.0/24 network for my setup with 192.168.2.1 assigned to the router and 192.168.2.200-254 range setup for the DHCP clients.
However, I've observed the same issue with default setup where router had 192.168.1.1 IP address.
Not sure how this is relevant because this issue is on the LAN part, but router is connected to the provider vie Ethernet cable.
Yes, I'm talking about VPN server embedded to the router.
I don't follow this question: "What happens if you use ISP detected DNS with VPN disabled and enabled?"
The router receives, "detects", DNS server IP addresses from the ISP on the startup and uses them to resolve domain names and it shouldn't change when VPN enabled/disabled.
Even if router would itself would switch to some other DNS servers when VPN is on, why it would start refusing DNS connections from the LAN clients?
What is the brand and model# of the ISP modem/ONT?
Just checking to see if same thing happens when using ISP DNS vs using custom which you stated using with VPN enabled.
Has this ever worked on this router or is this new to you?
