Alan Dayley wrote:
> Alan Dayley said:
>
>>DNS
>>- Hans is the keeper of the DNS. As I recall, he had some adjustments
>>to make that may have been the issue. I don't know if he has done said
>>adjustments.
>>
>>Host Company
>>- The host company reported to me that there is no problem or blocker on
>>their end. I must take them at their word unless evidence shows
>>otherwise.
>>
>>User ISPs
>>- That leaves the individual ISPs. Users with problems need to report
>>their ISP and complain. Unless there is a better way to pursue this leg
>>of the stool.
>
>
> Replying to myself after reviewing Patrick's traces from last month, I
> tend to discount the User ISPs as the problem. I think all of his
> failures first point to DNS or the hosting provider as the problem since
> either of those would have such a wide-spread effect.
>
> Alan
The most significant evidence is the sudden blackhole in the traceroute
immediately before the web site IP. DNS failures should fail to resolve
an IP to even *begin* a traceroute.
Here is the original email:
http://lists.plug.phoenix.az.us/lurker/message/20050420.225411.e46500a8.en.html
Note that lists is on a different server from www. Failures occur on the
machine/IP immediately preceeding the actual server.
Pings work. If they were just filtering traceroutes (why.. I don't know)
then all traceroutes should fail. But the same orgination points seem to
have web page access as well.
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss