| reply to Selenia
Re: [TWC] TWC DNS servers dont respond after awake from sleep said by Selenia:Step 1: Make sure that Windows is not set to put the network interface to sleep. Known to cause issues, especially behind some routers or with certain network adapters. It's even happening occasionally on my wifi-connected Android phone. I have only default settings on the Windows network adapters, and they work fine everywhere else.
said by Selenia:Step 2: Tell them to shove that Ubee modem so far up their behinds that it will never see the sun again. Interesting. I just had my Ubee swapped out 2 days ago, and the DNS problems seemed to get worse.
With the prior Ubee, a DHCP lease renewals fixed the problem. I didn't run Wireshark then, so I am not clear if it was the same problem as now, but now Wireshark now clearly shows DNS non-response for several minutes at a time. Why DHCP lease renewals worked? Beats me! I doubt the new DHCP leases would have specified different DNS servers.
This is really throwing me for a loop, though, because I don't know what specifically in the Ubee would be blocking DHCP responses! |
|
 DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8 | Are you wireless clients set to use the Ubee as a DNS forwarder or are the clients contacting the DNS servers directly?
What are the actual client configured DNS server IPs?
If it's using the default gateway IP as the DNS server IP, then the Ubee is configured as a forwarder and may be crashing randomly. Renewing the DHCP lease my force a restart of that process on the Ubee.
--
If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes. |
|
| said by DrDrew:Are you wireless clients set to use the Ubee as a DNS forwarder or are the clients contacting the DNS servers directly? I'm not home right now, but DHCP is telling us to use the actual TW DNS servers. The Ubee is not doing its own DNS. |
|
