Port 53 is used by built in router function

Online play isn't supposed to be 100% flawless but i'm looking for a fix for those 20% of players that i just cant seem to play with.

My network is all hardwired; linksys wrt1900ac router; Cisco DPC3008 modem; Charter ISP

My router is configured: UPnP enabled; no port forwarding (explained below); Xbox is set to DMZ using the mac address;

Only 1 xbox in the house; a laptop is online almost 24/7 as well; and sometimes i'll have my android connect to the same network; very rarely i'll have a friends laptop on the network as well.

The modem is not a gateway - and the problem with portfowarding is that there's a built in smart-wifi app which the router uses port 53 to manage the network, with no possibility of disabling said software unless i run custom firmware.

--- The built in function has the issue where if i port forward "53" my whole network crashes (e.g. cant obtain IP); and if i only port forward 80, 88, and 3074 when i test connection on my xbox i receive a strict/moderate NAT

Running a tracert to xbox.com comes back as follows:

Tracing route to xbox.com [134.170.29.82]

over a maximum of 30 hops:

1 3 ms 4 ms 3 ms Lin***192.168.1.1]

2 20 ms 11 ms 13 ms (public ip)

3 11 ms 11 ms 11 ms ISP HOP 1

4 22 ms 13 ms 13 ms ISP HOP 2

5 13 ms 13 ms 14 ms ISP HOP 3

6 21 ms 13 ms 13 ms ISP HOP 4

7 25 ms 24 ms 30 ms ISP HOP 5

8 24 ms 38 ms 24 ms ISP HOP 6

9 22 ms 21 ms 25 ms xe-2-1-2-0.wst-96cbe-1b.ntwk.msn.net [198.200.130.30]

10 23 ms 23 ms 22 ms ae0-0.wst-96cbe-1a.ntwk.msn.net [204.152.140.105]

11 * * * Request timed out.

12 * * * Request timed out.

13 75 ms 74 ms 74 ms ae1-0.cys01-96cbe-1a.ntwk.msn.net [191.234.80.28]

14 75 ms 75 ms 76 ms ae7-0.cys01-96cbe-1b.ntwk.msn.net [191.234.81.247]

15 * * * Request timed out.

16 * * * Request timed out.

17 101 ms 108 ms 89 ms 191.234.85.12

18 * 87 ms 89 ms ae17-0.atb-96cbe-1a.ntwk.msn.net [191.234.84.2]

19 * * * Request timed out.

20 101 ms 102 ms 106 ms ae1-0.bn1-96c-2b.ntwk.msn.net [204.152.141.39]

21 * * * Request timed out.

22 * 191.234.78.55 reports: Destination net unreachable.

Trace complete.

Is this true packet loss? i'm still learning about networking, a little at a time; if it is, is there anything i can do to improve my connection further aside from buying a router that doesn't have said complication?

:)

 

Port Forwarding

Port 53 is used for DNS. Don't forward this port. The list of "open" ports requires that these ports are open, not forwarded. Port 53 can be left out of port forwarding (as well as 80 and 88). When you reboot and check the network settings of the Xbox you
should be good. Also do not forward 80. I also did not forward 88.

Check your ports against any ports that might be used by other equipment as you could mess up access by that equipment:

en.wikipedia.org/.../List_of_TCP_and_UDP_port_numbers

Lastly, use your own router, Have your ISP put your modem (which they provide is commonly used as a router) into Bridged Mode and let your router handle all of the traffic. Get a good network person to set this up for you. Your ISP router is usually junk,
and it has its own firewall. So, if you set ports on your router, but your ISP's equipment is not configured, well then you are wasting your time.

 

Lag during gameplay

Hey Coleman

Lag in games, as well as general connection issues, can be caused by not having an open NAT. If you have access to the admin functions of your router, open the following ports:

Port 88 (UDP)

Port 3074 (UDP and TCP)

Port 53 (UDP and TCP)

Port 80 (TCP)

These are the ports required for Xbox Live. Can you try opening them and let us know if it helps?

 

Usually only port 3074 needs to be forwarded to open the NAT.

There is a bug in the xbox where the NAT can go strict if you use instant on mode.

This happens even if the ports are correctly forwarded. I don't think it happens to everyone though but it happens to me.

Try switching the console to energy saving mode then switch it off.

First try using UPnP exclusively then switch the console on and check the NAT.

If that doesn't work then set up DMZ again while console is switched off then try again.