Forum Discussion

Tutor

Oct 30, 2017

Forcing Router DNS / Blocking Port 53 @ Clients

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 o...

NETGEAR Employee Retired

Nov 01, 2017

Welcome to the community, 80sTiger

Which model number you're working on previously?

Can you post screenshots of the configurations?

Did you try resetting the unit?

80sTiger

Tutor

Nov 01, 2017

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
NETGEAR Employee Retired
Nov 03, 2017
Let me check this with our engineers.
- 80sTiger
  Tutor
  Nov 04, 2017
  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.
  - ElaineM
    NETGEAR Employee Retired
    Nov 08, 2017
    Kindly register your device so that we may log a case.