Dear colleagues,
The RIPE NCC provides secondary DNS for some reverse DNS zones using a
server called ns.ripe.net. In the early days of IPv6, this server was
also given another name, ns-v6.ripe.net, and some users used this name
in their IPv6 reverse DNS zones.
Last year, we contacted these users
> On 24 Apr 2018, at 15:33, Anand Buddhdev wrote:
>
> Now that the name ns-v6.ripe.net is no longer in use by anyone, we are
> going to delete it from the ripe.net zone.
Anand, could you clarify what you mean by “no longer in use”? Has it gone from
all the reverse zones that referenced it? Ar
On Tue, Apr 24, 2018 at 03:48:39PM +0100, Jim Reid wrote:
> > On 24 Apr 2018, at 15:33, Anand Buddhdev wrote:
> >
> > Now that the name ns-v6.ripe.net is no longer in use by anyone, we
> > are going to delete it from the ripe.net zone.
>
> Anand, could you clarify what you mean by “no longer in
On 24/04/2018 16:48, Jim Reid wrote:
Hi Jim,
> Anand, could you clarify what you mean by “no longer in use”? Has it
> gone from all the reverse zones that referenced it? Are no more queries
> for ns-v6.ripe.net hitting the ripe.net name servers?
There are no domain objects in the RIPE Database,
> On 24 Apr 2018, at 15:51, Job Snijders wrote:
>
> At least this is a good sign:
> https://github.com/search?q=ns-v6.ripe.net&type=Code
Thanks Job. Though I wasn’t thinking (or caring) about github crapware. I was
thinking about stuff that might have been written for internal use -- say at
On 24 Apr 2018, at 16:07, Anand Buddhdev wrote:
>
> Even if we *could* look at the queries, and they showed queries for
> "ns-v6.ripe.net", it doesn't mean that the name is in use.
Well, I would say that if the name’s in the query traffic, that means it’s “in
use”. For some definition of that t
Hi,
On Tue, Apr 24, 2018 at 04:25:59PM +0100, Jim Reid wrote:
> Thanks Job. Though I wasn???t thinking (or caring) about github crapware. I
> was thinking about stuff that might have been written for internal use -- say
> at an ISP -- and would only show up whenever these scripts or whatever mad
On 24/04/2018 17:33, Gert Doering wrote:
Hi Gert,
> OTOH it might be worth some considerations about "soft landing" - that
> is, point ns-v6.ripe.net at a new server that logs queries, respons to
> everything with SERVFAIL (or forwards to ns.ripe.net?), and if you see
> significant traffic, cont
> On 24 Apr 2018, at 16:33, Gert Doering wrote:
>
> Hi,
>
> On Tue, Apr 24, 2018 at 04:25:59PM +0100, Jim Reid wrote:
>> Thanks Job. Though I wasn???t thinking (or caring) about github crapware. I
>> was thinking about stuff that might have been written for internal use --
>> say at an ISP -
On 24/04/2018 17:28, Jim Reid wrote:
Hi Jim,
> Well, I would say that if the name’s in the query traffic, that
> means it’s “in use”. For some definition of that term. YMMV.
I respectfully disagree. A human may idly query the name ns-v6.ripe.net
out of curiosity. If they happened to use one of t
> I respectfully disagree. A human may idly query the name
> ns-v6.ripe.net out of curiosity. If they happened to use one of these
> shiny new resolvers that do pre-fetching to keep an entry alive, the
> queries for that name will persist for a long time, and perhaps even
> forever. I don't conside
Hi,
On Tue, Apr 24, 2018 at 05:46:50PM +0200, Anand Buddhdev wrote:
> On 24/04/2018 17:33, Gert Doering wrote:
>
> > OTOH it might be worth some considerations about "soft landing" - that
> > is, point ns-v6.ripe.net at a new server that logs queries, respons to
> > everything with SERVFAIL (or f
12 matches
Mail list logo
