|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||||
|
|||||
|
I'm online with Wanadoo Anytime in the UK (dial-up connection) and I own www.jeopardylane.com which I bought through www.1websitehosting.biz and is hosted (I think) by www.drs-servers.com. Ever since jeopardylane.com moved servers in November I've often had difficulties accessing the website and its mail server because of DNS_TIMEOUT errors. These aren't linked - sometimes I can get to both the site and mail server, sometimes neither, and sometimes just one or the other.
Having asked a few people, I found this only affected those whose ISP is Wanadoo (formerly Freeserve). I e-mailed Wanadoo about it and received the following reply: Quote:
So, I forwarded the e-mail from Wanadoo to 1 Website Hosting and got the following reply: Quote:
If it's normal for the name servers to not respond to ICMP ping packets, why does 207.44.193.1 not do it but 207.44.192.91 does? 207.44.193.1 does not respond when queried for the SOA record or version number while 207.44.192.91 does either. I e-mailed the hosting company to ask this question but got no reply. I e-mailed them again last week to ask if there had been any progress, and got an automated reply saying that they are moving support from email to a web based help desk system. No problem, I posted the Wanadoo e-mail again on there and started again, while also asking if 207.44.193.1 could be the problem. My reply yesterday was: Quote:
Oh well. I'm at my wit's end - can any of the knowledgeable people who frequent this forum please point me in the right direction as to what I should be doing? Thanks very much. |
|
#2
|
||||
|
||||
|
Well if it really is dns related problems then yeah, I can help. The next time a site doesn't work, I want you to execute the following command at the DOS prompt:
nslookup www.thesitethatdoesnotwork.com Then paste for me the results. That way I can verify whether or not it is a DNS related problem and what sort of problem it is.
__________________
Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links: Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts |
|
#3
|
|||
|
|||
|
Because I'm using Windows 98SE I don't have nslookup so I used the nslook utility from www.pcpitstop.com, will that do the job?
Right now, when I try to access www.jeopardylane.com in Internet Explorer I get the following error: Quote:
I opened a DOS prompt and typed 'nslook www.jeopardylane.com' and got the following result: jeopardylane.com 207.44.192.91 Meanwhile, Outlook Express cannot access my e-mail and fails with this error: The host 'mail.jeopardylane.com' could not be found. Please verify that you have entered the server name correctly. Account: 'webmaster@jeopardylane.com', Server: 'mail.jeopardylane.com', Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 11001, Error Number: 0x800CCC0D However, if I type "http://jeopardylane.com" into Internet Explorer instead of "http://www.jeopardylane.com" the site appears. Does any of that help at all? |
|
#4
|
||||
|
||||
|
I don't know anything about nslook utility. I don't know if it's using your system, your resolver list, or directly resolving the domain. So let's use ping instead.
ping www.jeopardylane.com ping jeopardylane.com Show me the response. Don't just tell me if it timed out or not, I want to see the actual response exactly. Then, since your problem is intermittant, make sure the www doesn't work and the root works still in IE. |
|
#5
|
|||
|
|||
|
Everything's working fine at the moment (typical!) but in case it's of any importance, I just realised I'd entered jeopardylane.com as 207.44.192.91 in my HOSTS file previously, hoping it might cure the problem on my machine (it didn't). I've deleted the HOSTS file now so it won't affect any further results.
|
|
#6
|
|||
|
|||
|
It hasn't happened again yet where www.jeopardylane.com fails and jeopardylane.com works, but right now neither are accessible, nor the mail server.
I tried these commands, and the responses are shown below. nslook www.jeopardylane.com - Unknown host www.jeopardylane.com nslook jeopardylane.com - Unknown host jeopardylane.com ping www.jeopardylane.com - Unknown host www.jeopardylane.com. ping jeopardylane.com - Unknown host jeopardylane.com. Could the situation where www.jeopardylane.com failed but jeopardylane.com worked be down to the HOSTS file that I've since deleted? |
|
#7
|
|||
|
|||
|
At last!
www.jeopardylane.com - fails in Internet Explorer jeopardylane.com - works in Internet Explorer nslook www.jeopardylane.com - jeopardylane.com 207.44.192.91 nslook jeopardylane.com - jeopardylane.com 207.44.192.91 ping www.jeopardylane.com: Pinging jeopardylane.com [207.44.192.91] with 32 bytes of data: Reply from 207.44.192.91: bytes=32 time=252ms TTL=48 Reply from 207.44.192.91: bytes=32 time=249ms TTL=48 Reply from 207.44.192.91: bytes=32 time=236ms TTL=48 Reply from 207.44.192.91: bytes=32 time=244ms TTL=48 Ping statistics for 207.44.192.91: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 236ms, Maximum = 252ms, Average = 245ms ping jeopardylane.com Pinging jeopardylane.com [207.44.192.91] with 32 bytes of data: Reply from 207.44.192.91: bytes=32 time=239ms TTL=48 Reply from 207.44.192.91: bytes=32 time=247ms TTL=48 Reply from 207.44.192.91: bytes=32 time=236ms TTL=48 Reply from 207.44.192.91: bytes=32 time=234ms TTL=48 Ping statistics for 207.44.192.91: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 234ms, Maximum = 247ms, Average = 239ms e-mails aren't accessible at the moment. Does this shed any light on the situation? |
|
#8
|
||||
|
||||
|
If www.jeopardylane.com is failing in IE, but ping seems to find it just fine and also jeopardylane.com works in IE, then the problem is most likely a misconfigured webserver.
__________________
Up the Irons What Would Jimi Do? Smash amps. Burn guitar. Take the groupies home. "Death Before Dishonour, my Friends!!" - Bruce D ickinson, Iron Maiden Aug 20, 2005 @ OzzFest Down with Sharon Osbourne Puzzle of the Month solved by Keath and KevinADC, superior perl programmers of the month Looking for a perl job with kick-*** programmers in a well-known NASDAQ listed tech company with branches in the US and Europe? We're hiring. PM me for details. Requirements |
|
#9
|
||||
|
||||
|
Yes, I think it's a combination of things. The webserver is probably misconfigured as scorpion says. ping was able to get the IP for both the root and www domains. At that point it couldn't be a DNS problem.
However, then you used nslook and got unknown host errors. I wish you had shown me the pings instead. Currently the domain is hosted on 2 servers. One of them is down as of this post. Perhaps the other one occasionally drops as well, or perhaps nslook is just a dumby and wasn't trying both servers when its first attempt (the down server) failed. |
|
#10
|
|||
|
|||
|
Quote:
How do you mean? When I used ping, I was getting exactly the same message as I posted - "Unknown host jeopardylane.com". Thanks for all your help so far, it's given me some hope at least! ![]() |
|
#11
|
||||
|
||||
|
Well if ping is also returning unknown host, that is when you should use the hosts file to assign the domain the IP. If that fixes ping resolution, but the ping results time out and you can't browse the site, it's cause the site is down. Nothing you can do about that except complain to them.
|
|
#12
|
|||
|
|||
|
This is odd... Both www.jeopardylane.com and jeopardylane.com aren't working in Internet Explorer at the moment and nslook and ping gave "Unknown host jeopardylane.com" for both addresses. I put jeopardylane.com as 207.44.192.91 in my hosts file, and:
nslook jeopardylane.com: jeopardylane.com 207.44.192.91 nslook www.jeopardylane.com: Unknown host www.jeopardylane.com ping jeopardylane.com: Pinging jeopardylane.com [207.44.192.91] with 32 bytes of data: Reply from 207.44.192.91: bytes=32 time=261ms TTL=48 Reply from 207.44.192.91: bytes=32 time=241ms TTL=48 Reply from 207.44.192.91: bytes=32 time=240ms TTL=48 Reply from 207.44.192.91: bytes=32 time=238ms TTL=48 Ping statistics for 207.44.192.91: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 238ms, Maximum = 261ms, Average = 245ms ping www.jeopardylane.com: Unknown host www.jeopardylane.com. And yet still neither www.jeopardylane.com or jeopardylane.com works in Internet Explorer, despite jeopardylane.com pinging correctly... |
|
#13
|
|||
|
|||
|
SilentRage - Basically, I did as you said and used the HOSTS file to assign the IP, and once I'd done that, 'ping jeopardylane.com' worked fine (i.e. it didn't timeout). The site still didn't work though, and neither did 'ping www.jeopardylane.com' (Unknown host www.jeopardylane.com).
Do you have any further ideas? Does it still look like a misconfigured server? |
|
#14
|
||||
|
||||
|
yep very mysterious. Ok, so I'm doing you and myself a favor here. I can't guarantee that when it works for me it isn't working for you without having some means of checking both locations in real time rather than through posts that takes ages to get noticed and read. So here's a little script |