Network issue with the IPv4 site or delayed response.
Network issue with the IPv4 site or delayed response.
Hi there, you're facing an unusual issue where websites with IPv4 addresses are unreachable. Requests often time out or load quickly before the timeout occurs, usually after 10-15 seconds. Restarting your router resolves the problem, but a simple reconnect doesn't work. During these errors, you can ping websites normally with typical latency and no packet loss. IPv6 sites like YouTube or Facebook remain accessible all the time. Your DNS settings are using the internet provider's servers, even though you've tried switching to Google or Cloudflare without success. Using a VPN (like PIA) during these errors allows you to access all sites. The issue happens across all devices—wired and wireless, desktop and mobile—and your ISP is only using DS Lite instead of native Dual Stack. I'm not sure if that affects the problem. Have anyone else experienced this? You've already reached out to your router manufacturer, but you're unsure if they'll find a solution.
It seems your router isn't getting an IPv4 address from DHCP. IPv6 assignment functions differently and usually responds more quickly than v4. I experienced this issue before power outages. My router took longer to start than the modem, so it sent its DHCP request before the modem was ready. It appears my router had a DHCP client bug—it would only send one request, and if it timed out, it stayed without an IPv4 address. Next time, check your router's admin page for its WAN address. If it's missing or shows 0.0.0.0, that’s likely the cause. If you face the same problem, it’s a bug; DHCP should retry automatically. Consider updating your router's firmware and see if it resolves the issue. In my case, an ASUS router fixed the problem via a firmware update, but I used a custom script to detect and fix similar conditions.
I'm reaching out to the router manufacturer and my ISP. I've also read some posts from others who used 8.8.8.8 and 8.8.4.4 as alternatives for their IPv4 DNS, which seemed to resolve the problem. I'll give it a shot. Testing takes a bit of time because the issue happens occasionally. My router has a functional WAN address and shows both IPv6 and IPv6+AFTR (DS Lifte) connections. According to the logs, it hasn't lost power. I'll check again next time it occurs.