To set a static IP on an Xbox Series X or Series S, navigate to Settings > General > Network settings > Advanced settings > IP settings and switch from Automatic to Manual. Enter your chosen IP address, subnet mask, and default gateway, then save. The whole process takes under two minutes once you have those three values in hand — the rest of this article shows you exactly how to find them without guessing.
Why a Moving IP Breaks Xbox Networking
Your router's DHCP server hands out IP addresses from a pool each time a device connects. Most of the time your Xbox lands on the same address it had before, but leases expire, routers reboot, and the pool can shift. When the Xbox ends up on a different address, any port forwarding rule or DMZ entry you configured on the router silently breaks — those rules are pegged to a specific IP, not to a device name.
The most visible symptom is NAT type toggling from Open to Moderate between gaming sessions for no obvious reason. Rerunning the NAT test sometimes clears it temporarily because UPnP remaps the port, but the root cause — an address that moves — keeps coming back. Port forwarding works by telling the router that inbound traffic on a specific port should go to a specific local IP. When that IP changes, inbound traffic lands at the old address, which may now belong to a different device or nothing at all. Locking the address down breaks that cycle permanently.
Four Values You Need Before Opening the Xbox Menu
Gather these from a device that is already connected to your network before you touch the Xbox settings. Having them written down means you will not need to back out halfway through.
1. Your Router's Gateway Address
The gateway is the router's own IP on the local network. Common defaults are 192.168.0.1, 192.168.1.1, 10.0.0.1, and 192.168.2.1 — but the actual value depends on your hardware and firmware. Do not guess. Look it up on a connected device:
Write down that address. You will enter it into the Xbox Gateway field, and you may also use it as your DNS server if you want to route DNS through the router.
2. Subnet Mask
Home networks almost always use 255.255.255.0. Confirm it from the same output — on Windows it appears on the Subnet Mask line, on macOS as the Subnet value. Entering it incorrectly (a very common typo is 255.255.255.255) will not produce a save error on the Xbox, but the console will silently lose the ability to route traffic off the local segment, cutting off Xbox Live entirely.
3. A Free IP Address Outside the DHCP Pool
The static IP you assign must sit in the same subnet as the gateway but outside the range your router's DHCP server hands out dynamically. If you pick an address inside that range, the router may eventually assign the same IP to a phone or laptop, and both devices will see intermittent drops that are genuinely hard to trace back to a conflict.
To find your DHCP pool range, log into the router admin panel by typing the gateway address into a browser. Look for a section labeled DHCP Server, LAN Settings, or similar. The pool start and end addresses are displayed there. If the gateway is 192.168.1.1 and the pool runs from 192.168.1.100 to 192.168.1.200, any address from .2 to .99 or .201 to .253 is safe. Pick one and write it down.
4. DNS Servers
You have three solid choices: the router's gateway IP itself (it forwards queries to your ISP's DNS upstream), Google Public DNS at 8.8.8.8 with 8.8.4.4 as secondary, or Cloudflare at 1.1.1.1 with 1.0.0.1 as secondary. All three work reliably with Xbox Live. If you set a public DNS directly, be aware it bypasses any DNS-based parental controls or filtering configured on the router.
Step-by-Step: Setting the Static IP on Xbox Series X or S
With your values ready, follow these steps:
- Press the Xbox button to open the guide. Select Profile & system > Settings.
- Select General, then Network settings.
- Select Advanced settings.
- Select IP settings. The current mode reads Automatic. Change it to Manual.
- Enter your static IP address, then your subnet mask, then your gateway address. Use the on-screen keyboard — on some firmware builds, hold LB or RB to move between the three fields.
- Confirm and save. The console disconnects briefly and reconnects.
- Back in Advanced settings, select DNS settings. Set it to Manual if you want specific DNS servers, or leave on Automatic to inherit from the router. If DNS stops resolving after the change, return here and set Manual with the gateway IP or a public DNS as the primary.
Xbox OS updates occasionally reorganize or relabel these menu items. If you do not see IP settings directly under Advanced settings, look for an IPv4 Settings option or an Edit button beside the currently displayed IP address. The function is always present; only the label can change between firmware versions.
Verifying the Change from the Xbox
After saving, return to Network settings and run Test network connection. A clean pass with no errors confirms basic connectivity is intact. Go back into Advanced settings and check that the IP displayed matches the address you entered — not a 169.254.x.x address. An address starting with 169.254 is a self-assigned APIPA address, which means the Xbox failed to apply the manual settings, most often because of a typo in the gateway field. If you see one, re-enter the settings carefully and save again.
Verifying from Another Device on the Same Network
For an independent check, try to reach the Xbox from a computer on the same network:
Replace 192.168.1.50 with the address you assigned. The Xbox firewall typically blocks ICMP ping, so no reply does not necessarily mean the IP is wrong. A more reliable test is a DNS query through your gateway:
Replace 192.168.1.1 with your actual gateway. A valid DNS response confirms the network path through your router is intact — a solid proxy for the Xbox being able to reach Xbox Live through the same path.
Testing NAT Type After the Change
If fixing NAT type was the reason you came here, go to Settings > General > Network settings and select Test NAT type. The result should show Open.
If it still shows Moderate or Strict, the static IP is a prerequisite that is now in place — but the complete fix also requires port forwarding rules on the router pointing inbound game traffic to that IP. A static IP alone does not open NAT; it ensures port forwarding rules stay pointed at the right device rather than silently pointing at an address the Xbox no longer owns. Check Microsoft's Xbox support pages for the current list of ports required by Xbox Live services, as these are updated with platform revisions, and set those forwarding rules in your router to point at the static IP you just assigned.
The More Permanent Fix: DHCP Reservation on the Router
Setting the IP manually on the Xbox is the quicker path, but it has one weak point: a factory reset of the console wipes the setting and the console reverts to dynamic assignment. The more durable solution is a DHCP reservation configured on the router instead.
A reservation instructs the DHCP server to always hand the same IP to a specific MAC address. The Xbox stays on Automatic, receives the reserved IP on every connection, and requires no static config stored on the console. Port forwarding rules remain permanently valid. When the Xbox requests an address, the router responds with the reserved IP rather than the next dynamic slot — the exchange is identical to normal DHCP from the console's perspective.
To find the Xbox's MAC address: Settings > General > Network settings > Advanced settings. Note the Wired MAC or Wireless MAC depending on how the console is connected. Use the one that matches your active connection type.
Then log into your router admin panel and find the reservation section. Paths vary by brand and can shift between firmware versions — check the manufacturer's support pages if the path below does not match what you see:
- TP-Link (tplinkwifi.net or 192.168.0.1): Advanced > Network > DHCP Server > Address Reservation
- Netgear (routerlogin.net or 192.168.1.1): Advanced > Setup > LAN Setup — Address Reservation table at the bottom
- ASUS (asusrouter.com or 192.168.1.1): LAN > DHCP Server > Manually Assigned IP Around the DHCP List
- Xiaomi / Mi (miwifi.com): More > LAN > DHCP Static IP
- Orbi (orbilogin.com or 192.168.1.1): Advanced > Setup > LAN Setup > Address Reservation
- Linksys (linksyssmartwifi.com or 192.168.1.1): Connectivity > Local Network > DHCP Reservations
- OpenWrt: Network > DHCP and DNS > Static Leases
- DD-WRT: Services > Services > Static Leases
Enter the Xbox's MAC address and the IP you want it to receive, save, then power-cycle the console. Verify in Advanced settings that the displayed IP matches the reserved address.
Common Mistakes and Misdiagnoses
Picking an IP Inside the DHCP Pool
An address inside the dynamic range is the most common mistake. Your router may assign the same IP to another device within hours or days. Both devices see intermittent drops with no clear error message. Check the pool boundaries in your router's DHCP settings before committing to an address and stay outside them.
Entering the Wrong Subnet Mask
255.255.255.255 instead of 255.255.255.0 is a very common typo. The Xbox saves the wrong value without error, but the console loses the ability to reach the gateway. If all connectivity disappears immediately after applying manual IP settings, open Advanced settings and verify the subnet mask is 255.255.255.0.
DNS Stops Working After Switching to Manual
On some Xbox firmware builds, setting IP settings to Manual while leaving DNS on Automatic causes DNS resolution to fail. The network connection test passes — the route to the gateway exists — but Xbox Live sign-in, party chat, and the store all time out because DNS queries are not resolving. Fix it by going to Advanced settings > DNS settings, setting it to Manual, and entering the gateway IP or a public DNS (8.8.8.8) as the primary server.
A 169.254 Address After Applying Settings
If the console shows a 169.254.x.x address after you save, the manual settings failed to take effect. The Xbox fell back to APIPA self-assignment because it could not confirm the gateway is reachable — most often a typo in the gateway field. Re-enter the settings, match the gateway exactly to what ipconfig /all or networksetup -getinfo showed on your computer, and save again.
Carrier-Grade NAT Blocking Open NAT Entirely
If your router's WAN IP — visible on the router's status page — begins with 100.64 through 100.127, your ISP is using carrier-grade NAT (CGNAT). Your home router is not the only NAT layer between the Xbox and the internet. Port forwarding on your home router will not open NAT in this scenario because inbound connections never reach your router; they are blocked at the ISP's NAT layer upstream. Assigning a static LAN IP is still worth doing for local stability, but getting Open NAT behind CGNAT requires a dedicated public IP from your ISP (available on request from some providers) or a gaming VPN that provides its own NAT traversal.
2026 Notes: IPv6, DoH, and DNSSEC
Most home routers now assign both IPv4 and IPv6 addresses simultaneously, and Xbox Series X|S uses IPv6 for Xbox Live traffic when the network supports it. IPv6 is handled automatically through stateless address autoconfiguration — no manual steps needed on the console. What to watch for: if you set a manual IPv4 DNS server but leave IPv6 DNS unset, queries that travel over IPv6 may fall back to the router's default forwarder instead of your chosen server. For consistency, set an IPv6 DNS address as well. Cloudflare's is 2606:4700:4700::1111 and Google's is 2001:4860:4860::8888.
DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) are not directly configurable on the Xbox console as of current firmware. The practical path to encrypted DNS for console traffic is enabling DoH at the router level, which is natively supported on ASUS Merlin firmware, OpenWrt 22.03 and later, and certain TP-Link AX-series routers in recent firmware. One configuration on the router covers all devices on the network without any per-device setup required.
DNSSEC validation is performed upstream by whichever resolver the Xbox queries. Both Google's 8.8.8.8 and Cloudflare's 1.1.1.1 validate DNSSEC by default, so pointing the console at either provides DNSSEC coverage without additional configuration. For a reference on the DNS protocol underpinning all of this, RFC 1035 defines the DNS message format and name resolution process implemented by every resolver in the chain.
Final Checklist
Before calling the job done, confirm each of the following:
- Advanced settings shows the IP address you assigned — not a 169.254.x.x APIPA address.
- Test network connection passes with no errors.
- Xbox Live sign-in works and the Microsoft Store loads.
- Test NAT type shows Open — and if it does not, port forwarding is the next step, not the IP assignment itself.
- No other device on the network is reporting connectivity problems — check the router's connected device list for any duplicate IP entries.
If you configured a DHCP reservation on the router rather than manual settings on the Xbox, power-cycle the console after saving the reservation. The address shown in Advanced settings must match the reserved IP before the task is complete.