What's new

How to get VPN to pass Internal DNS to client?

kfmfe04

Occasional Visitor
I have a DNS server that services public names for external IPs and internal names for the intranet. That set-up has been tested and works fine.

Recently, I got the built-in VPN server to work on the N66U - well, at least I can get on the internal subnet. However, the wrong DNS server is being passed through to the client:

N66U: 192.168.11.1 (STOCK FW: 3.0.0.4.260)
DNS server: 192.168.11.3
VPN client: 192.168.11.245

Pinging IPs works fine, but DNS lookups for local machines fail. When I try:

OSX_BOX$ scutil --dns | grep nameserver\[[0-9]*\]
nameserver[0] : 192.168.11.1
nameserver[0] : 192.168.11.1
nameserver[0] : 192.168.11.1
nameserver[0] : 192.168.1.1

So the VPN is designating itself (192.168.11.1) as the DNS server rather than the internal DNS server, 192.168.11.3 that I really want.

VPN Server/VPN Details/Connect to DNS Server automatically = YES
LAN/DHCP Server/Enable DHCP Server = YES
LAN/DHCP Server/RT-N66U's Domain Name = mydomain.com
LAN/DHCP Server/IP Pool Starting Address = 192.168.11.32
LAN/DHCP Server/IP Pool Ending Address = 192.168.11.244
LAN/DHCP Server/Default Gateway = 192.168.11.1
LAN/DHCP Server/DNS Server = 192.168.11.3

How do I tell the VPN Server to pass 192.168.11.3 as the DNS server to VPN Clients?
 
Last edited:
Solved From Client-Side

SOLVED The problem is on the client side.

Now that I think of it, it makes perfect sense - the client picks the DNS servers it wants, so on the OSX settings for the VPN client, I found the window for picking my internal DNS.
 
Similar threads
Thread starter Title Forum Replies Date
J Auto mounting internal microSD card of the RT-N66U ? ASUS N Routers & Adapters 5

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top