Registrars can takedown domains for net abuse, the main thing is their terms of service are between them and their registrants, they enforce their policies.
The easyDNS Plain English terms of service state domains will be taken down for net abuse, but if you want to compel a takedown from the outside because *you* say it's illegal, you need a court order.
The AUP is an agreement between a service provider and its customers. That's it. So the only two entities who have any say in whether there's an issue with the agreement are the two parties to it. Somebody else wants to shoehorn their own agenda into that, get a court order or go to hell.
That's why easyDNS can and does say that they are the arbiters of what constitutes a violation of the AUP.
Or as George W Bush would say, "We're the deciders".
You can sign your zones, etc. What you cannot yet do is submit DS keys to the regsitries directly (we're working on it) - this is a "gotcha" of our using openHRS on our backend and we've been in extensive communications with Tucows about this. We're hoping to have this resolved by end-of-summer.
In the meantime we are using ISC's DLV as a workaround.
If this is true (and I'll disclose here that I operate an ICANN accredited registrar myself) then my guess is any registrar doing this would be taking advantage of the 5-day grace period, in effect domain-tasting all of these regs and dumping the non-producing ones before the grace period expires for a full refund. This is currently being examined by ICANN but the loophole is still there.
In other words they could do this on a massive scale with a zero cost base and just keep the names that produce PPC revenues within the first five days.
Sorry for the self promotion with what follows, but when I first heard about this we added a "Guaranteed Lookup Privacy" statement to our easywhois portal, basically just going on record saying we have not, do not, will never do this. We feel it runs contrary to the interests of the customer.
"Still on hold with Network Solvent three years later on how the hell to transfer or delete a freakin HOST entry. Sigh."
If the host entry belongs to a domain you've moved over to us, email support and we can remove that host entry for you (only if we're the registrar of the parent domain)
It's actually less overhead for us if it was actually pointing where its supposed to be pointing. Unfortunately whoever transferred the domain to us never input their DNS settings so it was just sitting there on parked defaults when this happened.
We're trying to contact the owner/operators now and get the real IP's in place.
Hi, our update limit is 10 minutes (I think), anything less and you'll get a TOOSOON error. I see people updating us all the time with unneccessary updates (the new IP is the same as the old) and it doesn't bother us (not yet anyway).
Regarding your NAT issue, if you send in 1.1.1.1 as your IP address, we will take the peer address we see you coming from, not the private address of the router. This should work from any supported dyndns client including ez-ipupdate.
Slashdot Mirror
Registrars can takedown domains for net abuse, the main thing is their terms of service are between them and their registrants, they enforce their policies.
The easyDNS Plain English terms of service state domains will be taken down for net abuse, but if you want to compel a takedown from the outside because *you* say it's illegal, you need a court order.
The AUP is an agreement between a service provider and its customers. That's it. So the only two entities who have any say in whether there's an issue with the agreement are the two parties to it. Somebody else wants to shoehorn their own agenda into that, get a court order or go to hell.
That's why easyDNS can and does say that they are the arbiters of what constitutes a violation of the AUP.
Or as George W Bush would say, "We're the deciders".
Google's public DNS is a resolver service, Netsol's outage affects their authoritative servers.
We have it designated as "beta" right now, follow the status on http://easydnssec.com/
You can sign your zones, etc. What you cannot yet do is submit DS keys to the regsitries directly (we're working on it) - this is a "gotcha" of our using openHRS on our backend and we've been in extensive communications with Tucows about this. We're hoping to have this resolved by end-of-summer.
In the meantime we are using ISC's DLV as a workaround.
It was not easyDNS who "couldn't handle them", EVERYdns unplugged them. Not easyDNS
In fact wikileaks.ch started using easyDNS yesterday, wikileaks.nl will start tomorrow.
It was NOT easyDNS who "couldn't handle them", jeezus, you must be the LAST person alive on the planet who doesn't know this yet.
EVERYDNS unplugged wikileaks. NOT easyDNS. http://easyurl.net/a3191
In fact, as of yesterday wikileaks.ch ADDED easyDNS to their DNS.
If this is true (and I'll disclose here that I operate an ICANN accredited registrar myself) then my guess is any registrar doing this would be taking advantage of the 5-day grace period, in effect domain-tasting all of these regs and dumping the non-producing ones before the grace period expires for a full refund. This is currently being examined by ICANN but the loophole is still there.
In other words they could do this on a massive scale with a zero cost base and just keep the names that produce PPC revenues within the first five days.
Sorry for the self promotion with what follows, but when I first heard about this we added a "Guaranteed Lookup Privacy" statement to our easywhois portal, basically just going on record saying we have not, do not, will never do this. We feel it runs contrary to the interests of the customer.
"Still on hold with Network Solvent three years later on how the hell to transfer or delete a freakin HOST entry. Sigh."
If the host entry belongs to a domain you've moved over to us, email support and we can remove that host entry for you (only if we're the registrar of the parent domain)
It's actually less overhead for us if it was actually pointing where its supposed to be pointing. Unfortunately whoever transferred the
domain to us never input their DNS settings so
it was just sitting there on parked defaults when
this happened.
We're trying to contact the owner/operators now and get the real IP's in place.
We did not pull the DNS, the domain transferred
in and from the looks of it never set up their
DNS from the default settings.
We're trying to contact the owners right now.
Hi, our update limit is 10 minutes (I think), anything less and you'll get a TOOSOON error. I see people updating us all the time with unneccessary updates (the new IP is the same as the old) and it doesn't bother us (not yet anyway).
Regarding your NAT issue, if you send in 1.1.1.1 as your IP address, we will take the peer address we see you coming from, not the private address of the router. This should work from any supported dyndns client including ez-ipupdate.
for a search engine to allow regular expression searches. Now that would be sweet. (Unless there
is one already?)