Advanced settings should solve a defined problem. Port forwarding is for inbound reachability, QoS/SQM is for managing contention/latency, VLANs create policy boundaries, custom DNS changes name resolution, VPNs alter routing and trust paths, and bridge/access-point modes change which box performs routing. Changing them without a topology model can create problems that look unrelated.

Document the old state

Before changing LAN subnets, bridge mode, VLANs, routes or VPN policy, record the existing gateway, DHCP ranges, WAN mode and recovery address. A setting can be technically valid and still lock you out because your client remained on the old network.

Test one function at a time

After a change, verify local admin access, DHCP, DNS, internet reachability and the intended feature separately. This makes rollback possible and prevents several simultaneous edits from hiding the real cause.

Advanced configuration guides

Advanced settings have dependencies

Bridge mode can move NAT and DHCP to another router, VLAN changes can remove management access, VPN policy can install new routes and DNS, and port forwarding depends on the correct public and internal path. Draw those dependencies before you change multiple subsystems.

Define rollback before applying a risky change

Keep a local management path, the previous value, and a configuration backup where supported. If the intended feature does not improve, return to the known-good state instead of layering another advanced feature on top of an uncertain topology.

Video walkthrough for Advanced Router Settings: NAT, VPN, DNS, VLANs & More

Explains common DNS record types and how they fit together. DNS resolution is only one layer; a resolved hostname can still have a web, TLS or routing problem.