We have run into an issue where I was browsing Hewlett Packards website for driver downloads and got a page not found.
I bounced e-mails with the webmaster and they indicated all was fine on their side.
I go to:
which is the query page for DC5000 workstation drivers. When I select any of the three selections on the list I get page not found.
The page it is being redirected to is:
h20180.www2.hp.com resolves as 184.108.40.206
h18007.www1.hp.com resolves as 220.127.116.11
This problem started about 3 weeks ago, about 2 weeks ago patched up my server environment with all the MS patches currently available so I don't think that is the issue.
My enviroment is 1 Windows 2003 DC and 2 Windows 2000 DC's (1 acting as DNS). We are setup as Active Directory Integrated on DNS.
After HP said no problem I thought it might be our Firewall. I checked out the firewall and I was not dropping any packets when initiating the search.
I then plugged in a laptop between the router and firewall and configured an external address with an external DNS server and it worked.
I then went to my workstation and added an external DNS address. Thus, my workstation had my two internal DNS server addresses and the third external address of 18.104.22.168 and I was able to access the page.
The same day I was asked to do a Webex session and got the same problem w/o the external DNS address and using the external DNS address it worked.
The curious thing is that about 99.9% of websites are being resolved only a select few are not.
The reason it doesn't work is that the internal DNS server does not resolve that this name: http://h18007.www1.hp.com/
This was verified by doing an NSLOOKUP on the above address and it times out. External to our network it works.
Now all these pages worked approximately 3 weeks ago and now don't work. NO CHANGES have been made to my DNS server.
I even cleared the cache lookup on my two DNS servers. I also rebooted the DC with no luck.
My reverse DNS is setup as:
I'm not getting any relevant DNS event log errors when accessing the problem page.
OK, hopefully someone out there has some ideas.