Posted on July 29th, 2010 by Steve Cassidy
Why you might need to reboot your router to see a website
Just at holiday season begins, it looks very much as if various service providers and backbone connection suppliers have been very busy.
Lots of services have had their public IP addresses updated; I am getting calls from clients whose internal systems don’t genuinely use a domain name to get to a service. It’s not uncommon for all manner of software products (including router firmware) to let you type in www.pcpro.co.uk, and then look it up at that moment and convert it to 212.100.242.151 – which is what they then store for future connection attempts.
When we decide to change that underlying server address – which isn’t a bad thing to do, it’s a supported and allegedly seamless choice for a connectivity person to make – these various bits of software and hardware that use “one-shot lookup” simply fail to re-connect the PCs behind them.
According to a few webmasters, this effect includes some of the mass-market BT Broadband routers – you may well see a little note on some sites telling users to reboot their routers in order to bask in the full feature set of the site, for exactly this reason.
Of course, if you have gone away on holiday as all this has started, and you’re expecting to use remote access, or for your servers to carry on being available when they are behind a device which stores numeric IPs after you’ve typed in a name-style address, then you are out of luck. And you wouldn’t necessarily be able to test for this effect when you chose either your ISP or your router and firewall hardware.
On the bright side, a cold restart seems to sort out the problem, in most cases, so you won’t have to give the house-sitter, dog-walker or next-door neighbour the management interface password to your border device, while standing pumping Swiss francs into a callbox at the top of the Spluegenpass (or wherever).
Pull the power lead, count to 20, bang it back in, wait for the little red light to go green.
Tags: internet, IP address, router, server
Posted in: Hardware, Real World Computing
Follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.
3 Responses to “ Why you might need to reboot your router to see a website ”
Leave a Reply
Authors
- Barry Collins
- Chris Brennan
- Christine Horton
- Darien Graham-Smith
- Dave Stevenson
- Davey Winder
- David Bayon
- David Fearon
- Ewen Rankin
- Ian Devlin
- Jon Honeyball
- Jonathan Bray
- Kevin Partner
- Mike Jennings
- Nicole Kobie
- Sasha Muller
- Steve Cassidy
- Stewart Mitchell
- Stuart Turton
- Tim Danton
- Tom Arah
Categories
- About the bloggers
- Android App of the Week
- cloud computing
- Green
- Hardware
- How To
- iPhone App of the Week
- Just in
- Microsoft Office 2010
- Newsdesk
- Online business
- Random
- Rant
- Real World Computing
- Software
- View from the Labs
- Windows 7
- Windows 8
Archives
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
advertisement


July 29th, 2010 at 6:32 pm
Just got to love another cure that boils down to “turn it off and on again”.
July 30th, 2010 at 2:36 pm
If you have OpenDNS, instead of going through the fury of shutting down a router (among other appliances such as home server and VoIP phone), you can simply do the same process in a few clicks, and the best thing is everyone on OpenDNS benefits from it, as it updates their networks at the same time!
August 1st, 2010 at 1:37 pm
Not a I understand the problem, Richard. This is about the people who *don’t* use those services, or those whose routers “helfully” hold a local DNS cache irrespective of which upstream DNS is used, either by the router itself or by the machines behind the router.