Recent content by Piotr GRD

Yes, at the moment the "A" record for dy.exofire.net is correct. Maybe it has fixed by itself, maybe a staff did it without posting a word in here, or maybe when you was checking DNS settings in cPanel you did the "reset" and you have fixed it this way (my bet goes for the last scenario)...

dy.exofire.net is pointing to the IP 69.175.104.34, which is IP of the old unexisting "Chopin" server. There were many such DNS problems back in time when Boru/Chopin/Starka/Stoli/Lotus websites were moved to Absolut/Level/Vox, I'm surprised that after so long time such issues still exists. You...

I wonder... Are you aware that ns2 (108.178.57.230) does not work properly since 2012-12-07 ~00:52 UTC (for more than 10 days already)? If you'll try to send the DNS query to this server either for x10hosting.com or for x10premium.com or for x10.mx etc. the reply is "REFUSED" instead of proper...

DNS records on x10hosting nameservers still points your domain name to the IP of old not functional already "Chopin" server. booekaki.com. 86400 IN SOA ns1.x10hosting.com. no-reply.x10hosting.com. 2012062017 86400 7200 3600000 86400 booekaki.com. 86400 IN A 69.175.104.34 booekaki.com. 86400...

Unfortunatelly these are the DNS records for "oricocanada.x10.mx": oricocanada.x10.mx. 86400 IN SOA ns1.x10hosting.com. corey.x10hosting.com. 2012031600 86400 7200 3600000 86400 oricocanada.x10.mx. 86400 IN A 69.175.104.34 oricocanada.x10.mx. 86400 IN MX 0 oricocanada.x10.mx. oricocanada.x10.mx...

This should be done automatically by the administration for all moved from server to server domain names. Especially that this is free subdomain under x10.mx domain name. But as I wrote - this is most likely not the only problem as even if you'll ignore domain name system and you'll send HTTP...

These are the DNS settings for your domain name: rycon.x10.mx. 86400 IN SOA ns1.x10hosting.com. support.x10hosting.com. 2012080902 86400 7200 3600000 86400 rycon.x10.mx. 86400 IN A 69.175.121.66 rycon.x10.mx. 86400 IN MX 0 rycon.x10.mx. rycon.x10.mx. 86400 IN NS ns1.x10hosting.com...

Before publishing I've asked for any comments, suggestions etc. etc. from admins. The page looked exactly as it is now (except removed now full hostnames and except added now second time line in other time zone). I didn't receive any comment about using webhost logo either from x10Hosting admins...

Not the thing in being clear or not. The thing is in the way it's being wrote. "If I find IP I'll ban it" - why scare other people with bans?... Isn't this much better to simply send a normal message without scare with bans?... I've edited my previous message, check the stats.

@ Alex Mac Where? Whithin the words that he will ban the IP if found? For me it's not a valid request to turn the service off. It's not the right way of one admin communicate with other admin. I did wait many days before publishing the service for comments or yes/no/whatever - I did get only...

I only pointed that such silent acceptance exists. And yes, it's different I do provide service for x10Hosting USERS, so asking x10Hosting admins for comments is only my good will. I did follow their suggestion about not showing full hostnames, I did wait for some other comments - there was no...

What about when your GSM services provider, your bank, whatever makes changes in the agreement with you? There is usually a note that if you won't cancel your services in X days or you don't contact at all that's mean that you do accept new agreement. And I wrote specifically in the last reply...

@ Corey Note the difference that Pingdom waits 30 seconds and I wait only 15 seconds. So if the page is served in 15.001+ seconds Pingdom will say it is up, while my service will say "time out (>15s.) or offline". So the difference between the results will be for sure, but what's for we, human...

I'm not sure if I understand you correctly, but if you refer to me asking admins for responce before publishing my service - I've wrote twice that if they have nothing against I will make it public. After second time I had only one reply about hostnames which I removed and asked again (third...

@masshuu But only website owners will report the issue in here, regular visitors of these websites won't. And basing on my experience - some people that used to issues on (any) free webhosts already don't report problems so quickly, very often just wait and confirm they're obesrvations with...