In message , Edward Lewis writes:
>
> Mind you - I not all bugs are "serious" as in operations impacting. In
> this case, the name in question doesn't 'exist' so any access to it
> (WWW/SSH/FTP) is doomed anyway. Whether it's NXDOMAIN or NODATA, there's
> no or A record to be had. Yes, yo
In message , Edward Lewis writes:
>
> On 4/23/15, 2:45, "Micha=C5=82 K=C4=99pie=C5=84"
> wrote:
>
> >> Yes, its due to bug:
> >>=20
> >>=E2=80=A2 Fix RCODE when secondary NSD got transfer that includes
> >> deleted
> >>wildcard record. After deletion, NSD would serve NODATA, should be
> >
On 4/23/15, 2:45, "Michał Kępień" wrote:
>> Yes, its due to bug:
>>
>> • Fix RCODE when secondary NSD got transfer that includes deleted
>>wildcard record. After deletion, NSD would serve NODATA, should be
>>NXDOMAIN (thanks Michal Kepien).
>
>This is fun - I never expected this bug to be p
On Thu, Apr 23, 2015 at 08:45:01AM +0200,
Michał Kępień wrote
a message of 14 lines which said:
> This is fun - I never expected this bug to be publicly noticed for a
> TLD. It's only observable in the time span between wildcard record
> removal and the next run of "nsdc patch" on the slave
I
A reminder that the the early registration deadline for our Amsterdam
workshop is *this Friday* the 24th:
https://oarc-spring2015-amsterdam.eventbrite.com/
If you are planning to attend, please note that the registration fee,
increases from $150 to $250 for non-member attendees TOMORROW F
Robert Edmonds wrote:
>
> Interestingly, the two servers that return NOERROR are distinguishable
> from the others using fpdns:
>
> fingerprint (a0.nic.adult., 199.115.152.1): No match found
> fingerprint (a0.nic.adult., 2001:500:a0:0:0:0:0:1): No match found
Gosh, doesn't fpdns try versi
