|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Skywing <Skywing@valhallalegends.com> To: Jeremy Jackson <jerj@coplanar.net>, Suresh Ramasubramanian <ops.lists@gmail.com> Date: Sun, 16 Nov 2008 22:22:05 -0600 In-Reply-To: <1226880169.6912.321.camel@ragnarok> Cc: "nanog@nanog.org" <nanog@nanog.org> Errors-To: nanog-bounces@nanog.org Why not just return NXDOMAIN if you are going to all of that trouble and be= guaranteed that it'll work for standards-compliant caching resolvers? I d= on't see what would be available to gain by adding this extra complexity, a= nd there's certainly a (much) lesser guarantee, or so I would tend to belie= ve, that things will stop asking if they get an ICMP unreach as opposed to = an NXDOMAIN. - S -----Original Message----- From: Jeremy Jackson [mailto:jerj@coplanar.net]=20 Sent: Sunday, November 16, 2008 7:03 PM To: Suresh Ramasubramanian Cc: nanog@nanog.org Subject: Re: godaddy spam / abuse suspensions? 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 AM, James Hess <mysidia@gmail.com> 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. >=20 > Yes, and that'd make a good case for the good old ops practice of > dialing down the TTL for a while before any NS change is made. >=20 > --srs >=20 --=20 Jeremy Jackson Coplanar Networks (519)489-4903 http://www.coplanar.net jerj@coplanar.net
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |