|
Feb 25
2010
|
|
Sometimes I get some really strange problems to sort. Really random things. The following breakdown is an outline of the problem, random as it is I encountered today.
After completing a router upgrade for a client I set to work on the 'list' of things they wanted me to look at, and if you work in IT support you have no doubt worked through a few lists in your time. One of the things on the list was to do with a user preference for connecting to AOL's homepage to access Sport, News and Financial information, the financial information being the most critical.
The user automatically had the homepage set to a HP port of AOL when they opened the browser and had stuck with it, even grown to like it.
The URL is this - http://hp-commercial.my.aol.co.uk/?icid=desktop
In the middle of this page, is a widget that displays features across four pages with a selection of the latest from AOL News, AOL Sport and AOL Money. You click on a link and (obviously) it opens up a new window.
What was strange is that apparently, for the last several months, the financial links hadn't been working returning a 404.
So I looked at the links and could see they where directed to subdomains of AOL, sport.aol.co.uk, news.aol.co.uk and money.aol.co.uk. I went to each in turn and when I tried to go to money.aol.co.uk it resolves to www.dailyfinancial.co.uk.
The problem is that the HP port of this hasn't recognised the change! If you go to AOL directly and then move to the money section it ports over, but going from the homepage start listed above and you will get the 404.
This isn't a new problem, it has been there for months which got me thinking that the reason it hasn't been spotted or fixed, is that not many people stick with the registry hacked corporate changes that something like a HP desktop will be delivered with....or they don't care about myaol from HP...or they don't care about money, and therefore information about it.
DNS problems aren't always related to internal name spaces, and can catch a company like HP out. I am going to track how long it is before this gets fixed.








