The QoS Engine feature helps improve your network gaming performance by prioritizing the data flows of network applications. QoS is for maintaining a managed bandwidth for devices that are online at the same time so one doesn't hog the bandwidth.
Advanced DNS : When feature is enabled, your internet traffic will be protected by a security ready DNS server. This feature provides Anti-Phishing to protect your Internet connection from fraud and navigation improvements such as auto-correction of common URL typos.
Note:
When DNS Relay is enabled along with Advanced DNS feature, your workstations on the network that are obtaining an IP address from router's DHCP server will obtain 192.168.0.1 (router's IP address). However, traffic will still be protected. Although Advanced DNS feature is enabled, DNS IP address of your workstation can still be modified to the DNS server IP you desire. Please note that the router does not dictate the DNS name resolution when DNS IP address is configured on the workstation.
If you selected this option and have VPN or Intranet setup in your network, you can disable Advanced DNS service if you experience connection difficulties. Advanced DNS Services is a service held by Dlink that they maintain for DNS. Sometimes this works well for certain applications, some times it doesn't. Gaming and such, it's preferred to no use there services.
DNS Relay
When DNS Relay is enabled, the router plays the role of a DNS server. DNS requests sent to the router are forwarded to the ISP's DNS server. This provides a constant DNS address that LAN computers can use, even when the router obtains a different DNS server address from the ISP upon re-establishing the WAN connection. You should disable DNS relay if you implement a LAN-side DNS server as a virtual server.
Reserved IP addresses help maintain that each device keeps it's own uniquie IP address all the time to prevent conflicts and helps in trouble shooting. Also is needed for when you set up rules and options on the router, if you specify an IP address for an option, should the IP happen to change while using Dynamic IPs, this will break the rules and options. Reserved is preferred.
NAT Endpoint Filtering
The NAT Endpoint Filtering options control how the router's NAT manages incoming connection requests to ports that are already being used.
Endpoint Independent
Once a LAN-side application has created a connection through a specific port, the NAT will forward any incoming connection requests with the same port to the LAN-side application regardless of their origin. This is the least restrictive option, giving the best connectivity and allowing some applications (P2P applications in particular) to behave almost as if they are directly connected to the Internet.
Address Restricted
The NAT forwards incoming connection requests to a LAN-side host only when they come from the same IP address with which a connection was established. This allows the remote application to send data back through a port different from the one used when the outgoing session was created.
Port And Address Restricted
The NAT does not forward any incoming connection requests with the same port address as an already establish connection.
Note that some of these options can interact with other port restrictions. Endpoint Independent Filtering takes priority over inbound filters or schedules, so it is possible for an incoming session request related to an outgoing session to enter through a port in spite of an active inbound filter on that port. However, packets will be rejected as expected when sent to blocked ports (whether blocked by schedule or by inbound filter) for which there are no active sessions. Port and Address Restricted Filtering ensures that inbound filters and schedules work precisely, but prevents some level of connectivity, and therefore might require the use of port triggers, virtual servers, or port forwarding to open the ports needed by the application. Address Restricted Filtering gives a compromise position, which avoids problems when communicating with certain other types of NAT router (symmetric NATs in particular) but leaves inbound filters and scheduled access working as expected.
UDP Endpoint Filtering
Controls endpoint filtering for packets of the UDP protocol.
TCP Endpoint Filtering
Controls endpoint filtering for packets of the TCP protocol.
Formerly, the terms "Full Cone", "Restricted Cone", "Port Restricted Cone" and "Symmetric" were used to refer to different variations of NATs. These terms are purposely not used here, because they do not fully describe the behavior of this router's NAT. While not a perfect mapping, the following loose correspondences between the "cone" classification and the "endpoint filtering" modes can be drawn if this router is configured for endpoint independent filtering, it implements full cone behavior; address restricted filtering implements restricted cone behavior; and port and address restricted filtering implements port restricted cone behavior.