them from the ISC DLV TAR, as we have done for all
our other zones.
If you have any questions or concerns, please send email to d...@ripe.net.
Regards,
Anand Buddhdev
Senior Engineer
RIPE NCC
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http
egards,
Anand Buddhdev
RIPE NCC
u have any questions, please send an email to
Regards,
Anand Buddhdev
RIPE NCC
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVbaqyAAoJEBXgoyUMySoFkcwP/iFoS32eGZYdmTkyGoKvFZgS
6bdIVZcUNZzE3KEbLj9mtLG4pZIdDrCtAkEgg+ZRGwElCjzzrxTXybQxziAOz/JJ
Xy+FUpXy
s are
functioning as the hidden masters for ns.ripe.net, and the old server
(193.0.0.198) is no longer performing this function.
If you have any questions, please reply to
Regards,
Anand Buddhdev
RIPE NCC
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtool
roll the keys of all zones at the same time.
We will do this in batches, starting with a small number of reverse
DNS zones of the RIPE Meeting address space.
If you have any questions, please send an email to .
Regards,
Anand Buddhdev
RIPE NCC
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear colleagues,
I am happy to report that we have completed the roll-over of the keys
of all our zones, and upgraded the signatures to RSA/SHA256.
Regards,
Anand Buddhdev
RIPE NCC
On 26/11/15 12:01, Anand Buddhdev wrote:
> Dear colleag
ne issue we faced, and how we overcame
it. When rolling the algorithm of our zones, we followed the procedure
we had developed, taking care of this issue, and as a result, there
were no validation failures during the roll-over.
Regards,
Anand Buddhdev
RIPE NCC
-BEGIN PGP SIGNATURE-
Comment
installations or upgrades.
We apologise for any inconvenience caused. If you have any specific
questions please send email to .
Regards,
Anand Buddhdev
RIPE NCC
signature.asc
Description: OpenPGP digital signature
ddr.arpa.
66.in-addr.arpa.
Regards,
Anand Buddhdev
RIPE NCC
signature.asc
Description: OpenPGP digital signature
Hello Heike,
Thank you for reporting this. We're looking at it now. My analysis shows
that two out of 4 APNIC-operated zones are affected as well:
153.in-addr.arpa
163.in-addr.arpa
We are attempting to resolve this as soon as possible.
Regards,
Anand Buddhdev
RIPE NCC
On 17/03/2017
nelet exchange process.
Regards,
Anand Buddhdev
RIPE NCC
signature.asc
Description: OpenPGP digital signature
merged into
the parent zone we operate.
We are working with the other RIRs to look at the system, to see if we
can make it more robust, and perhaps faster, so that delegation
information can be exchanged more quickly, and in the event of errors,
also corrected more quickly.
Regards,
Anand Budd
-root-server-system
Best regards,
Anand Buddhdev
Senior Engineer, RIPE NCC
publishing
these legacy files, and all the zonelets will be published only with
their canonical names.
Regards,
Anand Buddhdev
RIPE NCC
Dear colleagues,
At the request of one of the RIRs, we have postponed this work to 5
September 2017.
Regards,
Anand Buddhdev
RIPE NCC
On 15/08/2017 14:44, Anand Buddhdev wrote:
> Dear colleagues,
>
> The RIPE NCC publishes DNS zonelets at the following URL:
>
> ftp://ftp.rip
On 15/08/2017 14:44, Anand Buddhdev wrote:
Dear colleagues,
This work is complete, and we're no longer publishing zonelets with
legacy file names.
Regards,
Anand Buddhdev
RIPE NCC
> Dear colleagues,
>
> The RIPE NCC publishes DNS zonelets at the following URL:
>
> ft
f you have questions or concerns you can contact the Programme Committee:
https://www.dns-oarc.net/oarc/programme
via
Anand Buddhdev, for the OARC Programme Committee
OARC depends on sponsorship to fund its workshops and associated social
events. Please contact if your organization is
int
details are at:
<https://indico.dns-oarc.net/event/28/call-for-abstracts/>
Anand Buddhdev, for the DNS-OARC Programme Committee
.
If you have any questions or concerns about this, please send an email
to .
Regards,
Anand Buddhdev
RIPE NCC
signature.asc
Description: OpenPGP digital signature
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/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/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
2018 - Submissions and Registrations open via Indico
13 Jul 2018 - Deadline for submission
17 Aug 2018 - Contribution list published
14 Sep 2018 - Full agenda published
06 Oct 2018 - Deadline for slideset submission
13 Oct 2018 - Workshop
Anand Buddhdev, on behalf of the joint Programme Committee
bmissions, so as to ensure the quality of the workshop, submissions
SHOULD include slides. Draft slides are acceptable on submission.
If you have questions or concerns you can contact the Programme Committee:
https://www.dns-oarc.net/oarc/programme
via
Anand Buddhdev, for the joint Pro
ansfer starts with the SOA record of the zone, and ends with
the same SOA record. That's how you know that the transfer is complete.
To learn more about zone transfers, see RFC 5936, section 2.2:
https://tools.ietf.org/html/rfc5936
Regards,
Anand Buddhdev
RIPE NCC
Good morning Måns,
We will come back to you shortly with answers to your and others'
questions in this thread.
Regards,
Anand Buddhdev
RIPE NCC
On 10/06/2019 09:22, Måns Nilsson wrote:
> Recently, a discussion regarding the checks performed by the NCC before
> reverse delegation is m
e hope to
have it implemented by the end of this year. Please accept our apologies
for not providing more information earlier.
Regards,
Anand Buddhdev
RIPE NCC
this condition as an error.
Regards,
Anand Buddhdev
RIPE NCC
, I will send a follow-up message.
Regards,
Anand Buddhdev
RIPE NCC
Dear colleagues,
This work has been completed successfully.
Regards,
Anand Buddhdev
RIPE NCC
On 03/03/2020 12:38, Anand Buddhdev wrote:
> Dear colleagues,
>
> The RIPE NCC runs a pair of hidden masters for transferring in zones
> from various sources, and distributiong these zo
experienced some failures if they had
cached signatures made by the old ZSKs.
We apologise for any operational problems this may have caused. We are
looking at the issue with the developers of our Knot DNS signer to
prevent such an occurrence in the future.
Regards,
Anand Buddhdev
RIPE NCC
developers of the DNSSEC signing software, and they are
investigating. We are also adding some extra monitoring to our
infrastructure, to detect such problems more quickly.
Regards,
Anand Buddhdev
RIPE NCC
with support for ED25519.
I don't have a date for you, but we hope to update Zonemaster to the
latest version very soon.
In the meantime, if you need to add or update a DS record for your
zones, please email d...@ripe.net with a complete copy of your domain
object, and we will do the updates for you manually.
Regards,
Anand Buddhdev
RIPE NCC
,
Anand Buddhdev
RIPE NCC
Dear colleagues,
I made a mistake in the date. It should have been Thursday 25 March (not
May). Apologies for this.
Regards,
Anand Buddhdev
RIPE NCC
On 18/03/2021 17:02, Anand Buddhdev wrote:
> Dear colleagues,
>
> Some time ago, our community asked us to implement the automatic up
can continue to validate our DNSSEC-signed responses
during the roll-over.
If you have any questions or concerns, please send an email to d...@ripe.net.
Regards,
Anand Buddhdev
RIPE NCC
-update/
We have also updated our requirements, whereby we will accept
well-provisioned virtual servers for hosting these services.
Regards,
Anand Buddhdev
RIPE NCC
delegation point of the /16-sized allocation (x.x.in-addr.arpa) occludes
(hides) NS records below it. This is how the DNS protocol works.
You'll have to find some way to convince the operator of the name
servers to add a delegation for you on their name servers.
Regards,
Anand Buddhdev
RIPE NCC
cussion about this, ideally via the DNS
Working Group mailing list. If you prefer to send your feedback directly
to us, you can email d...@ripe.net.
Regards,
Anand Buddhdev
RIPE NCC
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please vis
scans. The code that does the scans and checks does not invoke
Zonemaster, because it is only concerned with ensuring that the DNSSEC
chain of trust is correct.
Regards,
Anand Buddhdev
RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription opti
records will be imported
with the TTLs as published by the origin RIR.
Regards,
Anand Buddhdev
RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/dns-wg
Dear colleagues,
This work has been completed, and all zones are now being published with
lower TTLs.
Regards,
Anand Buddhdev
RIPE NCC
On 11/04/2022 14:44, Anand Buddhdev wrote:
Dear colleagues,
In 2021, we announced a plan to change the time-to-live (TTL) values in
the reverse DNS zones
e any significant changes.
Regards,
Anand Buddhdev
RIPE NCC
On 21/04/2022 09:07, Moritz Müller via dns-wg wrote:
Thank you Anand and team!
Out of curiosity, do you notice an increase in load at your servers?
--
To unsubscribe from this mailing list, get a password reminder, or change
Dear colleagues,
It has been more than 48 hours since we lowered the TTLs. We are *not*
observing any increase in query rates for NS or DS records. The rates
are at the same levels as before the change (around 12-13k q/s for each
of those types).
Regards,
Anand Buddhdev
RIPE NCC
On 21/04
support for the newest
DNSSEC algorithms, algorithm 15 (ED25519) and algorithm 16 (ED448).
Regards,
Anand Buddhdev
RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/dns-wg
it is
reasonable to use a CSK.
Regards,
Anand Buddhdev
RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/dns-wg
send email to
d...@ripe.net, with the details of the problem, and we will be happy to
help you.
Regards,
Anand Buddhdev
RIPE NCC
On 25/08/2022 09:23, Thierry Bagnoud wrote:
Hi,
do you have problem with reverse delegations (subnet 153.109.0.0/16) or
it's a problem for ARIN ?
Thanks for
of these zones to fail.
The full sunsetting plan, published last year, is available on RIPE Labs:
https://labs.ripe.net/author/anandb/retiring-nsripenet/
Regards,
Anand Buddhdev
-
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net
Dear colleagues,
This work is complete.
Regards,
Anand Buddhdev
RIPE NCC
On Tue, 14 Jan 2025 at 09:59, Anand Buddhdev wrote:
> Dear colleagues,
>
> On Wednesday 15 January, we'll be moving on to the final phase of removing
> our secondary DNS service for LIRs (ns.ripe.net)
address, so we did not see the bounces. In the last 2
notifications in November and December 2024, we changed the sender address
that could see the bounces. We sent the email to over 1000 addresses, and
there were around 100 bounces. In a small number of cases, all emails sent
to a zone's contact
50 matches
Mail list logo
