On Sat, 2004-06-26 at 15:51, Dossy wrote:
The other two machines on the network are fine and this one was working until Wednesday. Your quite right in that the DNS server is actually sitting on my internal server behind the firewall. The A record is not published externally. I suspected that this was a DNS problem as well given that the IP works however, and there is always a however, telnet to steve.festinalente.co.uk works. To answer the query in your other mail, I sent the host header thus:On 2004.06.26, Steve <[EMAIL PROTECTED]> wrote: > I have just tried http://steve.festinalente.co.uk:8000 from a browser on > a different machine and it is fine??? Do the other machines that don't work use the same/correct DNS server? Check their TCP/IP settings and see what DNS servers they're configured to use. steve.festinalente.co.uk has no IN A record on the published DNS servers, so in order for you to resolve it you must be using some hidden internal DNS server that has the record and thus doesn't query the root servers to try and find it.
telnet steve.festinalente.co.uk 8000
Trying 192.168.1.2...
Connected to steve.festinalente.co.uk (192.168.1.2).
Escape character is '^]'.
GET / HTTP/1.0
Host: steve.festinalente.co.uk:8000
HTTP/1.0 200 OK
Last-Modified: Sat, 26 Jun 2004 08:03:24 GMT
MIME-Version: 1.0
Date: Sat, 26 Jun 2004 15:02:00 GMT
Server: AOLserver/4.0
Content-Type: text/html; charset=iso-8859-1
Content-Length: 49
Connection: close
<html>
<head>
</head>
<body>
TEST
</body>
</html>Connection closed by foreign host.
As you can see, that resolves nicely.
Also, check HTTP proxy settings. If those other three browsers that don't work are configured to use a proxy, and that proxy doesn't know how to resolve steve.festinalente.co.uk, well, they won't be able to get to your server. The fact that going directly to the IP in the http:// URL works says this is most likely a DNS-related issue.
I agree but I can't see where. I've double checked and the browsers are not set to use a proxy server. Dig is resolving the address on my machine as is telnet above. If it was just a case of not being able to resolve it then the browser would return a could not be found message - as it does if I type http://dummy.festinalente.co.uk. To prove this point I just added test.festinalente.co.uk to the DNS with an A record of 192.168.1.2 and the browser happily works for http://test.festinalente.co.uk:8000/ but it won't work for steve.festinalente.co.uk on the same address?!?! Weird.
I'm beginning to suspect a problem with the browsers - which I've just realised are all gecko based. Maybe I have a corruption somewhere.
> Can anyone suggest what the significance of only seeing one nsd process > might be? Absolutely nothing. You only need one nsd process running. If you're on Linux and you're used to seeing multiple "processes" per nsd, that's because of LinuxThreads and older procps. I'm using procps 3.2.1 and nsd only shows up as one process, now.
Thanks, I have 3.1.15 and the other machine is on 3.1.11. Hopefully thats it although I never noticed it since upgrading until I had this problem.
Investigations continue.
Steve
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
