Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Just so you know, he and I had a long PM exchange last night, and, even though we never defined an exact cause, I feel that I got enough thanks.After all the time and effort rukbat gave up in an attempt to assist you, I think a small word of thanks wouldn't have gone amiss.
ya cause changing another router could mean some other issues. for example, i had a dlink router and for the longest time my battery wouldn't last 2 days. then i changed router for other reasons all of a sudden my battery life doubled. i would never have figured out that a router could drain your batteryJust so you know, he and I had a long PM exchange last night, and, even though we never defined an exact cause, I feel that I got enough thanks.
And I detest computer problems that can't be reproduced on demand - they're the most difficult ones to track down.
is this forum dead or nobody cares anymore
BTW, totally, totally wrong. The first time the router handshakes with the ISP, it gets the (usually 2) DNS server addresses that the ISP uses. And every time you reset it after that (most router menus have a "reget the connection" button somewhere in one of the menus) it gets the DNS server IP(s) again. (Most of the time it also gets them when the DHCP lease expires.)Your dns isn't supplied directly by your isp. Its configured into your router so unless you got it directly from your isp it will have been preset by the manufacturer, either directly or possibly when/if you ran through a router installation wizard.
BTW, totally, totally wrong. The first time the router handshakes with the ISP, it gets the (usually 2) DNS server addresses that the ISP uses. And every time you reset it after that (most router menus have a "reget the connection" button somewhere in one of the menus) it gets the DNS server IP(s) again. (Most of the time it also gets them when the DHCP lease expires.)
But using Google DNS or OpenDNS is probably the best way to start diagnosing this problem. If the ISP thinks of quality service as an expense, it may take them a while to notice that their DNS servers went down.
Then again, the cache in the router might, if left on long enough, become corrupted. (Although I've had SOHO Linkys run for 10 years without so much as looking at the case to see if it was still there. Not bad for $40, but if you take a look at their salary ranges, you'd better be sitting down. "You listed the Chief of Operations as a programmer.")
i think if the dns of the accuweather server did not change, it would not cause any issues. but i have no way of knowing exactly what happenedBTW, totally, totally wrong. The first time the router handshakes with the ISP, it gets the (usually 2) DNS server addresses that the ISP uses. And every time you reset it after that (most router menus have a "reget the connection" button somewhere in one of the menus) it gets the DNS server IP(s) again. (Most of the time it also gets them when the DHCP lease expires.)
But using Google DNS or OpenDNS is probably the best way to start diagnosing this problem. If the ISP thinks of quality service as an expense, it may take them a while to notice that their DNS servers went down.
Then again, the cache in the router might, if left on long enough, become corrupted. (Although I've had SOHO Linkys run for 10 years without so much as looking at the case to see if it was still there. Not bad for $40, but if you take a look at their salary ranges, you'd better be sitting down. "You listed the Chief of Operations as a programmer.")