ASUS Router Connected But No Internet After Firmware Update

ASUS router shows connected but no internet after a firmware update? Nine times out of ten it's a DNS or WAN handshake problem. Here's how to fix it fast.

So you flashed the latest ASUS firmware, the router rebooted, Wi-Fi comes up fine, devices get IPs — and nothing loads. The router's status page says "Connected" but the internet's dead. I've hit this on everything from an RT-AC68U to an RT-AX88U after a 3.0.0.4.388.x update. The culprit here is almost always one of three things: DNS resolution broken by the new firmware defaults, a stuck WAN DHCP lease, or the new firmware's WAN detection quirks. Let's go in order of how often they actually happen.

Cause 1: DNS is broken (the most common culprit)

This is the one that bites most people. ASUS firmware updates sometimes toggle on DNS-over-TLS or DNS Privacy defaults, or reset your custom DNS servers back to the ISP's, which then fail to respond. Your router has an IP, your devices have IPs, but nothing resolves. The telltale sign: you can ping an IP directly but not a hostname.

Test it from a wired machine:

ping 1.1.1.1

If that works but this doesn't:

ping google.com

You've got a DNS problem. Don't bother poking your clients' DNS settings — fix it at the router.

Log into the router at router.asus.com or 192.168.1.1. Go to WAN > Internet Connection > DNS Server. Set Connect to DNS Server automatically to No, then punch in:

  • DNS Server 1: 1.1.1.1
  • DNS Server 2: 8.8.8.8

Apply. While you're there, check the DNSPrivacy or DNS-over-TLS setting (it moved around between firmware versions — sometimes it's under WAN, sometimes under Advanced). Turn it off. The default DoT servers some ASUS builds ship with have been flaky for months, and they break resolution entirely if the upstream doesn't answer on port 853.

Reboot the router, not just Apply. I've seen the DNS setting stick but the resolver daemon not restart without a full boot on RT-AX58U and similar models.

Cause 2: Stuck WAN DHCP lease after the firmware update

Second most common. The firmware update resets the WAN interface, and the ISP's DHCP server is still holding your old lease tied to a released MAC or session. Your router asks for an address, the ISP either ignores it or hands back something useless. Check Network Map > Internet Status. If the WAN IP shows 0.0.0.0 or a 169.254.x.x address, that's your problem.

The fix isn't just a reboot — the ISP side needs to see a fresh request. Here's what actually works:

  1. Power down the router AND the modem/ONT. Leave both off.
  2. Wait a full 2 minutes. Not 30 seconds. ISPs release stale leases on their own clock.
  3. Power on the modem/ONT first. Wait for all lights solid (usually 60–90 seconds).
  4. Power on the router. Give it another 2 minutes.

If that doesn't do it, log in and go to WAN > Internet Connection > MAC Address. Set MAC Clone to Yes, then hit the Clone button next to your PC's MAC. Apply, then reboot the modem again. This forces the ISP's DHCP to treat you as a new device. I know it feels like a hack. It is. It also works when nothing else will.

One more thing — some ASUS firmware (notably the 388 builds) added WAN > DHCP Query Frequency. If yours is set to Aggressive, the ISP may blacklist you for hammering their DHCP server. Set it back to Normal.

Cause 3: The firmware update itself is borked

Less common, but if you've done both fixes above and you still have no internet, the update didn't take cleanly. Symptoms: the admin page is sluggish, some settings refuse to save, or the WAN status flickers between Connected and Disconnected.

First try a hard factory reset. Not the soft one. Hold the reset button on the back for 15 seconds while powered on, release, and wait for the router to come back up. Then reconfigure from scratch — do NOT restore a saved config file from the previous firmware. Old NVRAM settings are a common source of post-update weirdness, especially on the RT-AC86U and RT-AX86U.

If a factory reset doesn't fix it, roll back. ASUS keeps old firmware in their download archive. Grab the version you were on before, and flash it via Administration > Firmware Upgrade > Upload. Don't use the auto-update button for this — manual upload is more reliable, and you can pick the exact version.

A couple of specific duds worth naming: the 3.0.0.4.386.48260 release for the RT-AX88U and the 3.0.0.4.388.21224 for the RT-AX58U both had WAN issues reported widely on the SNB forums. If you're on either of those, roll back first and ask questions later.

After rolling back, turn off auto-update. Go to Administration > Firmware Upgrade and uncheck the auto-check. Wait a few weeks, check the SNB forums or the ASUS release notes for known issues, then update on your terms.

Quick reference

SymptomCauseFix
Ping IP works, ping hostname failsDNS broken by firmware defaults / DoTWAN > DNS Server — set manual 1.1.1.1 / 8.8.8.8, disable DoT, reboot
WAN IP is 0.0.0.0 or 169.254.x.xStuck DHCP leaseFull modem+router power cycle (2 min off), then MAC clone if needed
WAN flickers, admin UI sluggishBad firmware flashHard factory reset first, then roll back firmware version manually
ISP throttling / blocking after updateDHCP Query Frequency on AggressiveWAN > set DHCP Query Frequency to Normal

If none of that takes, plug a laptop straight into the modem and see if internet works. If it doesn't, the router isn't your problem — call the ISP. It happens.

Related Errors in Network & Connectivity
0XC0130007 Quick fix: STATUS_CLUSTER_NETWORK_NOT_FOUND (0xC0130007) 0X000009D3 Fix 0X000009D3 Remoteboot Server Connection Error 0X000004CE Fix ERROR_CONNECTION_ACTIVE 0X000004CE in 3 Steps 0X80340011 0x80340011 NDIS Adapter Not Ready — Real Fixes

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.