HI Guys. When I am trying to view my web page (www.smartly.co.il) by using the secondary address (http://m03.internetmailserver.net) the web site work perfectly. Base on the Winhost initial mail, I changed the DNS server name to ns1.Winhost.com ns2.Winhost.com ns3.Winhost.com Since then when I am trying to ping to my website (www.smartly.co.il) I am getting replay from 96.31.35.13, but when I am trying to see the web page I am getting error 500 and I cannot see my web page. I will appreciate any help since my web site is suspended Thanks In advance Nir\
Hi. Your site is coming up okay for me. It could be that you have a DNS or browser cache that is still pointing you the old location. It can take a bit of time for those name server changes to propagate everywhere.
Hi, Hank. Thanks for answer. Yes, you have been hosted by the old server (212.143.154.240) and not by Winhost server;as result of deploy DNS changes, I am sending this request as result I am afraid about the new host server is not working well for my site… When I am checking the web side on Winhost server by using the secondary DNS name "http://smartlyc.w01.Winhost.com", the web site is working well However when I am using “ns1.Winhost.com” DNS server I am getting resolve IP “96.31.35.13” and then the web page does not work. Is there any SLA for resolve ticket? I am asking this because I see that it is taking too long time to resolve failure by using mail discussion and this web site is critical for me….? is there any online metode link chat...? Thanks Nir
If the secondary url is working then our service is working. DNS caching issues are outside of any webhost's control. It can take about 2-3 days for the internet to work itself out over dns updates.
HI, So we are more tham 40 Hours after :-(.... The DNS migration has been complete; all resolve IP point to your server but the same failure appear!!! The secondary URL working well ... but the web site is not working What do I need to do in effort someone really will try to check the issue and not just telling me to wait? Thnaks Nir
You better check with your registrar again. I looked at two different whois records and both show that smartly.co.il is still using... DNS Servers: ns1.sitesdepot.com ns2.sitesdepot.com as the DNS servers and not Winhost. http://www.isoc.org.il/domains/whois.html When I ping smartly.co.il on my end it is not resolving to our web server but to an IP address I do not recognize. C:\>ping smartly.co.il Pinging smartly.co.il [212.143.154.240] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 212.143.154.240: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>nslookup > 212.143.154.240 Name: niraze.bb.netvision.net.il Address: 212.143.154.240 You'll need to contact your registrar again and make sure they update the name servers to... ns1.Winhost.com ns2.Winhost.com ns3.Winhost.com
Yes, you are absolutely right, after ~ 60 hours of web outage I made this change (212.143.154.240) in effort to terminated this “saga” by routing traffic to my old sweaty server… I am no longer able to support this sort of supporting service; it is not suitable for hosting business application, Hope the manager of this company will understand and think about “Online” service even base on payment; it is not sane debugging failure by mails with 1-4 hours of each interval!!! Hope, in next 2-3 days the DNS update will be completes and I will cancel my subscription at Winhost. Thanks Nir
Our hosting platform was set up and working. The secondary url/ftp was working fine. You stated so yourself in the previous response. To resolve the domain to our location, the customer must update their domain name server. We can't do this step for you. Only the domain owner can do this. The DNS update is one thing that needs to happen and then you have to wait for the new dns info to propogate through the internet. It can take a few days. Some ISPs update their local DNS fast while others may take some time. Also, if you mess up the dns update or keep messing with it, then you will continually have issues with DNS caching. The DNS update and DNS caching is not something that Winhost has any control over. You can keep blaming us but you are blaming the wrong entity. We can't provide an SLA on something we have no control over. No host can offer that.
HI Curtis. Please understand, I am not “blaming you or Winhost” ! All I said is, your provided service is not suitable for my needs, in case I needed to host “good will” website, I will defiantly chose your services as result of great package with wonderful prices. However in case of hosting “Business” website I doubt. Winhost support time frame is unacceptable for “Run time system”, it is not profitable to save some dollars and when there is a failure the web site is of order for long investigation process, in my case it was around 2.5 days Please understand that it is not related what was the root cause of the failure (My side or your side), debugging system by using mails thread with long intervals of hours between each answer is not sane for “Business” website!!! Hope, the company will understand and think about finding “Online” service solution, Personally, I would be ready to pay on it additional payment… Thanks Nir
I'm not sure what the expectation is. We host many personal and business websites here. We answered your questions and there was a need to update the domain name servers to resolve the domain to Winhost. This is a step that must be done by the customer and there is an unknown dns caching period that must pass before the domain is fully resolving to our location. This is just an inherent part of the internet. This is something that cannot be expedited by Winhost. From what I can see, there was also a mistake in the dns entry initially which needed to be corrected adding delay to the dns issue. We investigated the inquiry and responded that there was a DNS issue. The investigation did not take 2.5 days. No support/sales ticket was unanswered during new years. We also responded to these forum posts on new years. If we told you that there was a dns issue over the phone or through chat, it would not change the dns issue or expedite its resolution. The bottom line is that everyone who updates DNS has to wait through the DNS caching period.
