Hey guys... well... I was in my computer just now... rebooted and when I came back my main domain was resolving to some server in Brazil. In panic I tried some other domains I host. Apparently all the others are resolving Ok but then I went to:
http://www.dnsstuff.com/
And ran traceroute
Well... all domains in ns*.evservers.net caused a "Sorry, I could not determine the IP for 100porcentobike.com" error
and the onlydomain I have in ns*theplanet.com returned valid results
Addistionaly, I can't make my SMTP work after the outage. Running Plesk 7.5 and RedHat. Any suggestions? Manually starting the service sendmai returns sendmail: unrecognized service
In Plesk interface SMTP looks Ok, all green... but then I can't connect to SMTP server from my outlook and the service monitoring in commandserver.com shows that SMTP is down. Any kind sould with sugestions?
Full Version: ns*.evservers.net had a sudden problem?
Same thing for me. The ns5 & ns6.ev1servers.net nameservers are either timing out or returning wrong (old) IP addresses. So, my web sites are down and have been since the outage. I opened a ticket and exchanged PMs with Aaron last night. Unfortunately, the problem is still unresolved.
Are others seeing this problem? From linux, you can type "dig @ns6.ev1servers.net domain.com" (substitute your domain in for domain.com) to find out what IP that nameserver is telling the world.
For me, if I execute this dig command 6 times in a row, I'll get two different answers (wrong and right) about 50/50 or a timeout. It's like there is a conflict of some kind?? They said they fixed a conflict yesterday.
It doesn't matter from where I run the digs, I always get screwed up answers or timeouts. I've tried on my local computer, and on 5 different servers at various facilities of ThePlanet.com.
Are others seeing this problem? From linux, you can type "dig @ns6.ev1servers.net domain.com" (substitute your domain in for domain.com) to find out what IP that nameserver is telling the world.
For me, if I execute this dig command 6 times in a row, I'll get two different answers (wrong and right) about 50/50 or a timeout. It's like there is a conflict of some kind?? They said they fixed a conflict yesterday.
It doesn't matter from where I run the digs, I always get screwed up answers or timeouts. I've tried on my local computer, and on 5 different servers at various facilities of ThePlanet.com.
QUOTE (Hedges @ Jun 4 2008, 08:00 PM) 
Same thing for me. The ns5 & ns6.ev1servers.net nameservers are either timing out or returning wrong (old) IP addresses. So, my web sites are down and have been since the outage. I opened a ticket and exchanged PMs with Aaron last night. Unfortunately, the problem is still unresolved.
Are others seeing this problem? From linux, you can type "dig @ns6.ev1servers.net domain.com" (substitute your domain in for domain.com) to find out what IP that nameserver is telling the world.
For me, if I execute this dig command 6 times in a row, I'll get two different answers (wrong and right) about 50/50 or a timeout. It's like there is a conflict of some kind?? They said they fixed a conflict yesterday.
It doesn't matter from where I run the digs, I always get screwed up answers or timeouts. I've tried on my local computer, and on 5 different servers at various facilities of ThePlanet.com.
Are others seeing this problem? From linux, you can type "dig @ns6.ev1servers.net domain.com" (substitute your domain in for domain.com) to find out what IP that nameserver is telling the world.
For me, if I execute this dig command 6 times in a row, I'll get two different answers (wrong and right) about 50/50 or a timeout. It's like there is a conflict of some kind?? They said they fixed a conflict yesterday.
It doesn't matter from where I run the digs, I always get screwed up answers or timeouts. I've tried on my local computer, and on 5 different servers at various facilities of ThePlanet.com.
Oh Yeah! Now things make sense. Support said they fixed the issue with me. So I checked and looked Ok. I was happy. Just to be sure a few minutes later I tested again and it was resolving AGAIN to a server somewhere else.
But that's when I tarceroute from my server. From my office the problem is gone (by itself, nobody took action). So now if I traceroute from the office is Ok. If I traceroute from my own server it's kinda random... a few times correct, most of the times wrong. Crazy!
Glad for me to learn that I'm not alone; sorry for you...
Hopefully Aaron and the DNS team will run with the information we've provided here and in our respective tickets. Faulty DNS servers means no web or email service for our domains.
Hopefully Aaron and the DNS team will run with the information we've provided here and in our respective tickets. Faulty DNS servers means no web or email service for our domains.
I think they fixed it!
QUOTE (Hedges @ Jun 5 2008, 12:49 AM)
I think they fixed it!
Not here! Now the domain is again resolving to some other server, so I can't access eMail or website anymore (once again). Tracerouting from server continues to show random responses... either shows the right IP or the wrong one.
This is becoming pathetic now. Left a TT regarding this problem around 15 hours ago. Not a single answer to it. By now downtime for these domains (now it's more than one) is about 100 hors. Went to the chat support twice. First one have to face someone who's supposed to filtrate "calls". Who's so far (3 calls) is extremely annoying, saying nosense. First time I received at once an answer: nameservers are down. Well... anything except one domain was having problems, so..........
So far I lost 25% of my income. And because of this DNS issue I wil most probably loose another block of 15% which depend of a given client who's completely mad about one of this problematic domains.
Initially the problem was occuring only with my main and personal domain (coincidence, I believe), Annoying but I could take it for a while. Now it spreaded to other domains, one of them critical. 15 hours and no repply to a TT is becaming more than I can take. Patience is coming to an end here.
So far I lost 25% of my income. And because of this DNS issue I wil most probably loose another block of 15% which depend of a given client who's completely mad about one of this problematic domains.
Initially the problem was occuring only with my main and personal domain (coincidence, I believe), Annoying but I could take it for a while. Now it spreaded to other domains, one of them critical. 15 hours and no repply to a TT is becaming more than I can take. Patience is coming to an end here.
Oh boy... along the day, domains keep appearing and disappearing from nameservers there. And this goes not only to ev1servers namservers but also to theplanet.com nameservers.
Now a domain is there, visible to DIG command... in a hour is not there anymore... then another domain... then the first one is there again. What a nightmare. And they stopped update the status. Taking 10-15 hours to answer TT doesn't help. We are kept in completely darkness now about nameservers situation and nobody knows when will they return to normality.
Now a domain is there, visible to DIG command... in a hour is not there anymore... then another domain... then the first one is there again. What a nightmare. And they stopped update the status. Taking 10-15 hours to answer TT doesn't help. We are kept in completely darkness now about nameservers situation and nobody knows when will they return to normality.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.