dns problem?

I'm having a very strange problem, seemingly with dns.

the error I get is as follows:
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
An error occured while loading http://www.texaswest.com:


Timeout on server
Connection was to www.texaswest.com at port 80
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

OK now before everyone jumps to the normal 'dns problem' answers
please hear me out. <grin>

The box can get to other web sites just fine.
seems my local newspaper:
http://www.texaswest.com/

and my local noaa weather site:
http://www.srh.noaa.gov/radar/latest/DS.p19r0/si.ksjt.shtml

I can NOT get to these sites using their numbered ip's
like 208.62.120.227 for the texaswest.com site
and 63.77.98.76 for the srh.noaa.gov site

These 2 are the only sites I have found I have the problems with
I have tried using many different browsers and cleared their cashe's.
I have checked and rechecked the links for typos
(in fact have even tried using links on other web sites to get there)

-------------------------
Now the rest of the story (the part where it gets really wierder)

--using the same dsl modem
--thru the same switch to the router/firewall box
--thru the same external router/firewall box
--using the same hub
--all using fixed ips (isp as well as network) 
--no dhcp from the isp or the router/firewall on any of the boxes
--no proxys envolved
**all 6 other boxes on this network work just fine for the web sites in question!

--all /etc/resolve.conf files on all boxes remain the same  (no changes)
(and are the same as they have been for months/years)

--there is no firewalling active on this box.
--I have swapped out cables/nic cards(discrete-not onboard)/ports on the hub
--I have done a cold restart on everything the entire network
(unplugged everything from 120v and waited a few minutes)
from the dsl modem/switch/firewall/router-firewall/ thru to the boxes.

----------------------------
more data I have gathered trying to diagnose this:

the texaswest.com site is a part of scripps.com server group
I can get to this site:
http://www.scripps.com/corporateoverview/businesses/newspaper/sanangelo.shtml
but can not connect from there using their san angelo link
http://www.texaswest.com

also I tried and failed to access another texas paper 
http://www.texnews.com from it's web page:
http://www.scripps.com/corporateoverview/businesses/newspaper/abilene.shtml
again using the link on that page to try connecting to:
http://www.texnews.com
and that also failed.....

the srh.noaa.gov site is part of the noaa.gov server group
I can connect to this site:
http://www.nws.noaa.gov/
but from there i can not get to any of the http://www.srh.noaa.gov sites

I can make it to this site:
http://www.crh.noaa.gov/forecasts/TXZ072.php?warncounty=TXC451&city=San+Angelo
but not to the radar link which has the ".srh" 
rather than the ".crh" or the ".nws" prefixes
(that worked from the the http://www.nws.noaa.gov/ site)

--------------------------
traceroute results were as follow

on the box that fails
sam@205sid:~$ traceroute www.texaswest.com
traceroute to www.texaswest.com (208.62.120.227), 30 hops max, 38 byte packets
 1  192.168.6.1 (192.168.6.1)  0.845 ms  0.582 ms  0.403 ms
 2  bb1-sa-bvi1.wcc.net (208.31.186.1)  19.575 ms  19.404 ms  20.974 ms
 3  wl-bb1-sa.wcc.net (208.6.232.1)  19.840 ms  23.561 ms  19.507 ms
 4  wl-gld-5-0-1.wcc.net (63.175.2.50)  176.466 ms  183.755 ms  239.801 ms
 5  wl-wf-1-0-0.wcc.net (63.175.2.54)  29.257 ms  28.540 ms  28.738 ms
 6  dal-edge-11.inet.qwest.net (65.115.192.81)  30.273 ms  31.108 ms  33.241 ms
 7  dal-core-03.inet.qwest.net (205.171.25.153)  30.956 ms  30.483 ms  29.918 ms
 8  iah-core-03.inet.qwest.net (205.171.5.169)  37.714 ms  36.835 ms  37.068 ms
 9  atl-core-01.inet.qwest.net (205.171.8.146)  49.497 ms  48.927 ms  48.784 ms
10  atl-edge-17.inet.qwest.net (205.171.21.190)  50.671 ms  48.790 ms  48.550 ms
11  * * *
12  * * *


from one of the boxes that works
sam@ndahouse4:~$ traceroute www.texaswest.com
traceroute to www.texaswest.com (208.62.120.227), 30 hops max, 38 byte packets
 1  192.168.6.1 (192.168.6.1)  0.877 ms  0.655 ms  0.488 ms
 2  bb1-sa-bvi1.wcc.net (208.31.186.1)  19.969 ms  22.540 ms  19.340 ms
 3  wl-bb1-sa.wcc.net (208.6.232.1)  19.607 ms  19.729 ms  24.260 ms
 4  wl-gld-5-0-1.wcc.net (63.175.2.50)  22.167 ms  21.897 ms  33.745 ms
 5  wl-wf-1-0-0.wcc.net (63.175.2.54)  29.318 ms  32.304 ms  34.093 ms
 6  dal-edge-11.inet.qwest.net (65.115.192.81)  30.705 ms  30.122 ms  31.641 ms
 7  dal-core-03.inet.qwest.net (205.171.25.153)  33.651 ms  31.460 ms  30.285 ms
 8  iah-core-03.inet.qwest.net (205.171.5.169)  56.917 ms  38.118 ms  39.798 ms
 9  atl-core-01.inet.qwest.net (205.171.8.146)  49.946 ms  50.754 ms  48.717 ms
10  atl-edge-17.inet.qwest.net (205.171.21.190)  49.421 ms  48.988 ms  49.441 ms
11  * * *
12  * * *

--------------------------

further checking shows the following:
There are a few more collisions showing on the 205sid box
          RX packets:12909 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7793 errors:0 dropped:0 overruns:0 carrier:0
          collisions:381 txqueuelen:100
          RX bytes:30609861 (29.1 MiB)  TX bytes:3495578 (3.3 MiB)

with the ndahouse4 box running
          RX packets:35871 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32814 errors:0 dropped:0 overruns:0 carrier:0
          collisions:45 txqueuelen:100
          RX bytes:16117009 (15.3 MiB)  TX bytes:691516 (675.3 KiB)

But then I have been using the sid205 box more, and only checking 
a few things on the other one.

I'm wondering why it seems the sites in question are ....
down in the bowels of the internal dns servers on both sites
not sure what I'm trying to say there...??
Is there perhaps some timing issues with this box
when it is having wait to dig down into internal dns redirect servers
(but we're only talking one ms difference....)
that doesent make sence to me as the problem
that really doesn't make sence to me .. but I'm at the wild guessing point here


so I give up? What have I missed?
(my last payment to the 'Murphy protection rackets fund' went thru just fine)
the check didn't bounce, he ate all the pizza, and drank all the beer I left him...
shhh..... don't call it bribery he doesn't like that
he prefers calling it payment for "features" or "services 'not' rendered" <grin..sigh>

As I'm asking this question in many different places, you can see a compilation 
of what has been said and tried here:
http://www.jass-ltd.net/~blt/dns_problem.html

God Bless,
Sam Morgan
"linux -- the lifetime learning experience" 







  
God Bless,
Sam Morgan
--
"linux -- the lifetime learning experience" 
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers-35TzE1X9F6582KRnZfj+bdi2O/[email protected]
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers