Good job to all who were involved in the server change. However, I have had many more site crashes since the server was moved to the UK. Anyone else experiencing this?

Which sites? ours? I have not noticed any down time since we moved but then again I havent been on that much lately.

hi yabancianne -- i personally haven't experienced any 'crashes' myself since the server change but i am curious to know about the when, why and frequency you have experienced such 'site crashes'. any more details are welcome; also please bear in mind that it is not always the domain host in the UK to blame i.e. did your company network experience any networking problems of late or has Internet service from your ISP (most likely Turk Telekom) been a bit flaky recently? please let us know, also others are welcome to comment.

FD

Sure. Our company's hotel reservation system went bust last week (everything was backed up though); however, it didn't affect internet access at all. When I get an error message, it's usually after making a post or sending a PM. I usually receive the "white screen of death" and something along the lines of "URL cannot be found. Reason: DNS not recognized." I'll bet I'll get one after trying to post this message

i am sorry to say yabancianne that i won't be able (based on the information given by you) to give any conclusive answers as to why you have experienced any crashes nor to your question whether anyone else have had a similar experience. DNS stands for Domain Name Server and this type of server performs a vital service on the Internet, most importantly it performs tasks such as addressing and routing providing an IP address for hostnames and domain names, for example in URLs and e-mail addresses that humans find easier to work with.

a DNS is typically operated by your Internet Service Provider [ISP] or by a domain name hosting provider and sometimes large corporations operate their own (not sure if your company does). since the DNS performs an extremely vital service on the Internet every well-respected ISP or domain name hosting provider operates more than one (at least two) DNS (the secondary being a redundant system to the primary). it is therefore that the system is reasonably error-proof although not fail-safe. the cause for the error message you've been reporting may be one of many for example: - your ISP experienced fault with their DNS servers, - our hosting provider may have had problems with their DNS servers, your company may have mis-configured their Internet access or their proxy server if any, etc, etc.

to enable us to act on the problem you experience, we need more (detailed) information:

• hostname or IP address of the DNS;
• when the error took place (date/time);
• duration of the fault;
• how the fault occurred (description on your actions taken).
• can you replicate the fault

sorry to answer your question with more questions but unfortunately we cannot act on information not available to us or not having experienced the fault(s) ourselves.

FD

Just had one when clicking on the "Expat in Turkey Forum Index" link.
The message read as follows:

The requested URL could not be retrieved
________________________________________
While trying to retrieve the URL: http://forum.expatinturkey.com/index.php
The following error was encountered:
Unable to determine IP address from host name for http://www.expatinturkey.com
The dnsserver returned:
No DNS records
This means that:
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
Your cache administrator is bulent@tigin.net.

________________________________________
Generated Fri, 27 May 2005 19:41:56 GMT by proxy.gts.tigin.net (squid/2.5.STABLE1)

thanks yabancianne -- the error report you have provided us with was generated (as said by its footnote) by your company's proxy server: a gateway giving (shared) access to the Internet. shortly after the time you posted your message i made a Tracert route analysis to the DNS servers of our domain name hosting providers and find no error with them. your report plus my findings on the Tracert route analysis leads me to believe the error may be closer to your end i.e. within the company (although don't quote me on that... i am not the expert)

without getting into any more technical detail, i could offer to contact the cache administrator of your company's proxy server and try to see we can work together on resolving the issue. one more question though... do you only experience this type of error when trying to reach any page on expatinturkey.com domain or does this error message also appear when visiting different (in particular .co.uk) domain names?

FD

Thanks, FD. I only really get them when trying to access this site--but don't contact my cache administrator--then they'll know for sure that I'm on here during work!

you're welcome! i thought not to contact the administrator already hence me asking you first anyhow if your IT department wanted to find out they probably already did. the proxy keeps a cache (log) of all domain names/ IP addresses requested.

very little more i can do from here unless anyone else reports same error. mind you i suspect you experience this error intermittently and therefore it may be temporary (fingers crossed) in nature i.e. your ISP may suffer temporary problems with their DNS.

sorry i can't be of any more help -- FD