Can a GoDaddy (domain) abuse admin contact me off list?
Thanks,
Dustin
On Mon, 2008-11-17 at 05:15 +0530, Suresh Ramasubramanian wrote:
> On Mon, Nov 17, 2008 at 4:20 AM, James Hess <[EMAIL PROTECTED]> wrote:
> > One of the secondary/tertiary recursive resolvers may hand the client
> > a cached response that had been obtained before the registrar took any
> > action.
I would tend to believe,
that things will stop asking if they get an ICMP unreach as opposed to an
NXDOMAIN.
- S
-Original Message-
From: Jeremy Jackson [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 16, 2008 7:03 PM
To: Suresh Ramasubramanian
Cc: nanog@nanog.org
Subject: Re: godad
In message <[EMAIL PROTECTED]>, Jeremy Jackson writes:
> or how about using an NS that returns ICMP errors instead of NXDOMAIN,
> perhaps using anycast for reducing network load?
ICMP is not particularly useful unless the nameserver uses
connected sockets. Now that randomised por
or how about using an NS that returns ICMP errors instead of NXDOMAIN,
perhaps using anycast for reducing network load?
Would that stop the timeout errors? server is still lame, you just know
faster?
On Mon, 2008-11-17 at 05:15 +0530, Suresh Ramasubramanian wrote:
> On Mon, Nov 17, 2008 at 4:20
On Mon, Nov 17, 2008 at 4:20 AM, James Hess <[EMAIL PROTECTED]> wrote:
> One of the secondary/tertiary recursive resolvers may hand the client
> a cached response that had been obtained before the registrar took any
> action.
Yes, and that'd make a good case for the good old ops practice of
diali
It's also not effective in various situations.
The bad behavior is not disabling abused domains, it's the method used to do it
(by giving no answer instead of actively giving a negative answer).
When a http client asks recursive resolver A for an A RR, and no
response is received,
the client wil
Chances are if the domain has been sandboxed, it was because it was
involved in some kind of phishing scheme, not spam. This is the
typicaly way of mitigating fast flux botnets. So I don't agree with the
assessment that this is bad behavior on the part of GoDaddy - to the
contrary, they are actin
I don't think he wants the domain. The problem is Godaddy listing NS
records for some domains (for any reason) to only DNS servers that
were all down or didn't exist. The entry of only lame DNS servers is
an inconclusive situation and doesn't let a message be permanently
rejected as spam; it's
Name has been suspended for "supposed" abuse by the godaddy abuse team.
I believe the only recourse is to email [EMAIL PROTECTED] (cc
[EMAIL PROTECTED]) asking what they want to release the domain to
you. I believe the usual charge is like $75 or so.
--Rohan
On Sun, 16 Nov 2008 10:10:20 -0800
m
Hi gang,
I am looking into a dns problem. My resolvers are attempting to
resolve various hosts under "axonplatform.net", but it's nameservers
aren't responding, resulting in many many many repeated queries that end
up going nowhere. I dug around a bit and the nameservers for the domain
are
11 matches
Mail list logo
