[Pound Mailing List] we have a strange loop

[Pat Erler]

hi,

we use pound for some weeks now. suddenly we have this problem and just
don't know what is happening. maybe someone can help:


- pound's URL is www.photocase.com, the IP is 176.9.216.74, which is
also the IP for *.photocase.com (which might be important)
- the backend IIS (7.5 aka w2k8r2) are v011.photocase.com and
v012.photocase.com
- go to this URL: Loading Image... - it works
- go to this URL: Loading Image... - press F5
some times and you will get a 404
- now it get's crazy: when you use http://web-sniffer.net/ or something
similar and research http://v011.photocase.de/images/rssicon.gif you
will see, that the request goes not to the IP of the backend server
v011.photocase.com (176.9.216.58) but to the IP of the pound server
(176.9.216.74) - how does this happen?
- and - why is pound giving us a 404? the file in question is available
from both backend servers. we found, hat the 404 comes from http.sys - so
the request doesn't even reach the IIS - but, we can't find any log entries
in c:\Windows\System32\logfiles\HTTPERR\httperr1.log

we are dumbfounded. any ideas?

PAT

[Dave Steinberg]

Post by Pat Erler
hi,
we use pound for some weeks now. suddenly we have this problem and just
* pound's URL is www.photocase.com <http://www.photocase.com>, the IP
is 176.9.216.74, which is also the IP for *.photocase.com
<http://photocase.com> (which might be important)
* the backend IIS (7.5 aka w2k8r2) are v011.photocase.com
<http://v011.photocase.com> and v012.photocase.com
<http://v012.photocase.com>
* go to this URL: http://www.photocase.de/images/rssicon.gif - it works
* go to this URL: http://v011.photocase.de/images/rssicon.gif - press
F5 some times and you will get a 404
* now it get's crazy: when you use http://web-sniffer.net/ or
something similar and research
http://v011.photocase.de/images/rssicon.gif you will see, that the
request goes not to the IP of the backend server v011.photocase.com
<http://v011.photocase.com> (176.9.216.58) but to the IP of the
pound server (176.9.216.74) - how does this happen?
* and - why is pound giving us a 404? the file in question is
available from both backend servers. we found, hat the 404 comes
from http.sys - so the request doesn't even reach the IIS - but, we
can't find any log entries
in c:\Windows\System32\logfiles\HTTPERR\httperr1.log
we are dumbfounded. any ideas?

Your public DNS points v011.photocase.de to the .74 IP. Same for v012.
I think you need to fix your DNS and then start from scratch, and see
where you land. Make sure you clear your DNS caches too, and verify
that those hostnames resolve to the right IPs.

Regards,

[Pat Erler]

ok, we had a feeling that there is something wrong with our DNS provider
but couldn't put a finger on it, as from here it looks good. thank you!

PAT

Post by Dave Steinberg

Post by Pat Erler
hi,
we use pound for some weeks now. suddenly we have this problem and just
* pound's URL is www.photocase.com <http://www.photocase.com>, the IP
is 176.9.216.74, which is also the IP for *.photocase.com
<http://photocase.com> (which might be important)
* the backend IIS (7.5 aka w2k8r2) are v011.photocase.com
<http://v011.photocase.com> and v012.photocase.com
<http://v012.photocase.com>
* go to this URL: Loading Image...>- it works
* go to this URL: Loading Image...>- press
F5 some times and you will get a 404
* now it get's crazy: when you use http://web-sniffer.net/ or
something similar and research
http://v011.photocase.de/**images/rssicon.gifrequest goes not to the IP of the backend server v011.photocase.com
<http://v011.photocase.com> (176.9.216.58) but to the IP of the
pound server (176.9.216.74) - how does this happen?
* and - why is pound giving us a 404? the file in question is
available from both backend servers. we found, hat the 404 comes
from http.sys - so the request doesn't even reach the IIS - but, we
can't find any log entries
in c:\Windows\System32\logfiles\**HTTPERR\httperr1.log
we are dumbfounded. any ideas?

Your public DNS points v011.photocase.de to the .74 IP. Same for v012.
I think you need to fix your DNS and then start from scratch, and see
where you land. Make sure you clear your DNS caches too, and verify that
those hostnames resolve to the right IPs.
Regards,
--
Dave Steinberg
http://www.geekisp.com/
http://www.steinbergcomputing.**com/ <http://www.steinbergcomputing.com/>
http://www.redterror.net/
--