Forcing Router DNS / Blocking Port 53 @ Clients

Question

Having just upgraded to Orbi, trying to duplicate my configuration around forcing devices in my home to use the DNS defined manually in the router and not allowing individually connected clients to override with their own cited DNS servers. In my previous Netgear router/AP I went into SECURITY, then BLOCKED SERVICES and added a new rule to block PORT 53 for 192.168.0.2-192.168.0.254 (assuming the router itself @ 192.168.0.1 needed to be open/available). This worked great on my previous Netgear router, but now it blocks all DNS on all attached clients even when they haven't defined any DNS statically. Did something change or am I missing something ? Thx.

ElaineM · Answer

Kindly register your device so that we may log a case.&nbsp;

&nbsp;

ElaineM · Answer

Welcome to the community, 80sTiger

&nbsp;

Which model number you're working on previously?

Can you post screenshots of the configurations?

Did you try resetting the unit?

&nbsp;

80sTiger · Answer

Previous model was AC750/R6050 ... config screenshot below worked fine in previous router (DNS worked fine for 192.168.0.1 DHCP'd to clients, blocked any manual set DNS on clients), but now same config blocks all DNS at clients with new Orbi - nothing resolves. I have indeed rebooted.

ElaineM · Answer

Let me check this with our engineers.&nbsp;

&nbsp;

80sTiger · Answer

Many thanks for checking. Just to be clear, on the previous Netgear router, when I had this service blocked (DNS) on this IP range (.2-.254), excluding only the router itself from the range (.1) and pointing all clients to the router (.1) for DNS resolution, everything worked/resolved just fine, and if a client tried to manually override their local DNS (which is the router at .1 issued via the router's DHCP), then nothing on the client would resolve correctly as the DNS traffic is blocked. Thanks.

Forum Discussion

Forcing Router DNS / Blocking Port 53 @ Clients

5 Replies