DNS quit resolving for some of my WiFi clients (but not all of them)
Posted on 2014-09-25
Here is my problem:
All WiFi client devices can ping 18.104.22.168. Some WiFi clients can use DNS and others cannot. When a client connects the the WiFi SSID, the client device gets a DNS server assignment of 192.168.x.1 where 192.168.x.1 is the same ip address of the WiFi router on the "local network" side of the WiFi router. So, some clients can use DNS by sending their DNS requests to 192.168.x.1 while others cannot. This configuration was working for months and stopped working today. If I use the NSLOOKUP command in Interactive Mode (on a windows computer), NSLOOKUP works fine if I use an alternate DNS Server (22.214.171.124), however if I use NSLOOKUP with the 192.168.x.1 address, DNS fails.
Here is my configuration:
SonicWALL NSA 2400 - X1 port configured for Cox Communications Broadband Internet Access. SonicWALL port X3 assigned to internal private IP address LAN dedicated to multiple WiFi Routers. WiFi Routers are are NOT configured in Bridge Mode and are connected to a common Class-C, LAN private IP address space with a unique 4th octet.
The "Local Network" side of the WiFi Routers all have their own unique Class-C, Private IP address (or subnet) space for the wireless devices to connect to.
I have attempted to manually assign "known good" DNS servers to the DHCP scope the wireless router configuration, but when the client device connects it just get the IP Address of the WiFi Router not the DNS server I configured.