Edimax DNS errors on every device: a practical Australian guide
An Edimax router can be online while every phone, laptop and television reports a DNS error. The underlying problem is usually not a dead internet connection: DNS converts a domain name such as asha.org.au into the numeric IP address a device needs to reach a website.
Useful background on the local interface is in the Edimax setup guide. Before changing settings, check whether numeric addresses respond but domain names fail. That pattern points to name resolution rather than the modem, Wi-Fi radio or website itself.
The checks below move from a household-wide test to the Edimax WAN configuration. They account for Australian conditions, including NBN services, the mix of Telstra, Optus and Aussie Broadband connections, and network arrangements that differ from older ADSL installations.
Understand what the error means
Most Edimax firmware sends DNS queries to the resolver supplied by your internet connection, or to addresses entered in its administration interface. A router can therefore have a valid WAN address, working LAN connections and full Wi-Fi coverage while its DNS service still fails. The link between the router and the household is LAN addressing and DHCP, not the internet connection alone.
Messages such as ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN indicate that a name could not be resolved. A timeout suggests the resolver could not be reached; an NXDOMAIN response says the resolver returned no such name. Filtering, an incorrect manual address and an ISP outage can produce superficially similar symptoms, so record the exact wording on each device.
Treat a working IP ping as useful evidence, not proof. Some routers and networks block ICMP traffic, so a failed ping alone does not establish an outage. The more important comparison is whether a domain lookup succeeds from the same device using the home connection and mobile data.
Establish where the fault begins
Start with scope. Disconnect one affected phone from Wi-Fi and test it on mobile data, then reconnect it to the Edimax network. If an Australian website such as commbank.com.au opens on mobile data but not on Wi-Fi, the fault is probably in the home DNS path. A second device on the same Wi-Fi provides a useful cross-check; if every device fails identically, start at the router and ISP connection.
On a Windows PC, ipconfig /all shows the DNS servers handed out by DHCP. On macOS, scutil --dns provides similar resolver details. Run nslookup example.com, followed by nslookup example.com 1.1.1.1, to compare the normal resolver with a direct query. A successful second command points towards the router's configured DNS; two timeouts suggest a broader network or filtering issue.
Keep these tests separate from browser cache clearing. Flushing a DNS cache does not repair an unreachable resolver, and clearing browser data can hide useful error details. Note whether wired devices fail too, whether a guest network behaves differently, and whether the problem began after a firmware update, a new device or an ISP change.
Check the router's DNS configuration
Reach the Edimax administration page using the local address printed on its label or specified in its manual. Common defaults include 192.168.2.1 and 192.168.1.1, although the exact model and ISP-supplied configuration matter. The local address can often open the interface even while DNS is broken because it does not require an external lookup. If the page will not open, check that the client is connected to the router's own Wi-Fi or Ethernet subnet.
Open the Internet, WAN or DNS settings offered by that firmware and check the WAN status before editing anything. If DNS is set to obtain an address automatically, restore that option and save. For a controlled comparison, temporarily enter 1.1.1.1 as the primary resolver and, where the interface permits, 8.8.8.8 as the secondary. Do not copy an address from an unrelated troubleshooting guide because some providers use special resolver settings.
After saving, allow the router to reconnect and restart the client network connection. Phones, smart TVs and appliances may retain an old DHCP lease and continue using the former DNS server. Forgetting the network and joining it again renews those settings. If the fault followed a firmware update, check the release notes for DNS or WAN changes and use firmware intended for the exact model and hardware revision.
Rule out device and browser settings
Check for a device-level override before replacing the router. Android has a Private DNS setting that may specify a custom hostname instead of using the network's resolver; iOS commonly receives DNS from the router unless a VPN profile changes it. On Windows and macOS, VPN software, corporate security tools and filtering apps such as AdGuard or NextDNS can also redirect queries. Set these controls to Automatic or temporarily disable them for one controlled test.
An active VPN is a frequent culprit when only some applications fail. Privacy settings in a browser are less likely to cause a router-wide fault, but a browser extension that intercepts requests can affect one device. Avoid changing antivirus or TLS settings permanently. If an affected device works after its filtering or VPN settings are reset, the Edimax configuration may be sound.
Some failures occur after a broadband migration rather than inside the router. Older internal hostnames, split DNS rules and business routers can require a particular search suffix or private resolver. A captive portal is different again: hotel or airport Wi-Fi redirects unauthenticated traffic to a sign-in page, while a normal Australian home connection should not do this unless the ISP specifically requires portal sign-in.
Verify the WAN connection and operating mode
Check the operating mode against the physical wiring. In router mode, the Edimax obtains an internet connection using DHCP or PPPoE, runs DHCP for the household, and normally obtains DNS through its WAN. In access-point mode, it should bridge to an existing router, which then supplies both addresses and name servers. If the Edimax remains in access-point mode while the upstream router is disabled, devices will receive no usable network configuration.
An NBN connection in a Sydney, Melbourne or Brisbane home may run through a network termination device supplied by NBN. Connect the Edimax WAN port to the correct NBN equipment or the Ethernet connection specified by your ISP; a wall socket alone is not always a usable Ethernet WAN. Telstra, Optus and Aussie Broadband may provide different gateway settings, and some supplied routers are locked to their own configuration.
Enter WAN details only as instructed. Use dynamic addressing when the ISP says to use DHCP. Enter PPPoE credentials only when your provider supplies them and permits a third-party router. Save the ISP settings, including any static IP, subnet mask, gateway and DNS addresses, before attempting a factory reset. If both the Edimax and an ISP router distribute addresses, disable DHCP on one of them to avoid conflicting instructions.
Compare common causes and remedies
The most reliable diagnosis combines one scope test with one configuration check. Use the comparison below to identify the branch that matches your symptoms before changing hardware or making a broad reset.
| Possible cause | Quick check | Practical remedy |
|---|---|---|
| Router has an incorrect manual DNS address | Admin DNS fields differ from the ISP settings | Restore automatic DNS or temporarily test with 1.1.1.1 |
| ISP resolver is unavailable | Home names fail while mobile data works | Reconnect the WAN and contact the ISP if public DNS also fails |
| Device overrides the router | Private DNS, a VPN or filtering software is active | Return the override to automatic and retest |
| WAN or PPPoE settings are wrong | WAN shows disconnected or authentication failure | Apply the ISP-specified DHCP or valid PPPoE details |
| DHCP or operating mode is duplicated | Two routers assign addresses, or AP mode has no upstream router | Run DHCP on one device and restore the correct mode |
| Filtering or a captive portal intercepts traffic | Traffic redirects to a sign-in page or resolver traffic is blocked | Complete sign-in or allow the required resolver traffic |
Read the results in sequence. If numeric connectivity works, a direct query to 1.1.1.1 succeeds and the normal query fails, the Edimax is probably using the wrong resolver. If the direct query also times out, investigate filtering, the WAN connection and the ISP. A failure limited to one device belongs in its own DNS, VPN or network settings; a household-wide failure belongs at the router or provider.
Apply a focused recovery checklist
Use these actions in order and record the result after each change:
- Confirm the affected devices and the Edimax WAN status before changing any settings.
- Compare a domain lookup on the Edimax Wi-Fi with the same lookup on mobile data.
- Restore the router's DNS to automatic, or temporarily use
1.1.1.1as its resolver. - Remove VPN, private DNS and filtering overrides one at a time, then retest.
- Check router or access-point mode and match DHCP or PPPoE settings to the ISP instructions.
- Record the WAN configuration and any PPPoE details before considering a factory reset.
- Reboot the NBN equipment and Edimax in sequence, allowing the WAN link to settle.
Your next step is to note the exact DNS error on one affected device, then briefly switch that device to mobile data and try the same domain name to establish whether the failure follows the device or the home connection.