February 2019 - dns-wg - mailman.ripe.net

Call for contributions to the RIPE 78 meeting of the dns-wg
by Dave Knight 02 Apr '19

02 Apr '19

Dear colleagues, The RIPE 78 meeting in Reykjavik is a few weeks away and we’d like to form our agenda. Please submit your presentation ideas, or suggestions for discussions to <dns-wg-chairs(a)ripe.net>. Please don’t submit anything using the meeting submission web form, it’s not intended for submission of content to working groups. Thanks! dave, on behalf of the working group chairs

2 2

How to determine the last message in sequence in DNS TCP responce
by Владимир Мартьянов 27 Feb '19

27 Feb '19

I make DNS zone transfer request (aka AXFR) via TCP to the server. The answer is too big (>100Kb), so it could not be sent in one TCP message. So the server send me a sequence of messages. How can I determine which message is the last? I can't found anything about it's count in the first message. I can't found any special flag in the last one. I can't found anything about it in RFC1035. Could you please explain how to find "end of answer"?

3 2

New on RIPE Labs: Managing DNS Zones Using Git
by Mirjam Kuehne 04 Feb '19

04 Feb '19

Dear colleagues, Using zone files for managing the Domain Name System (DNS) zone data is the most basic and flexible way to manage the authoritative DNS data. In this post on RIPE Labs, Ondřej Caletka describes how the Git version control system can be used to store zone file history and protect against errors: https://labs.ripe.net/Members/ondrej_caletka/managing-dns-zones-using-git Kind regards, Mirjam Kühne RIPE NCC

1 0

DNSViz Relocates to DNS-OARC
by Matthew Pounsett 01 Feb '19

01 Feb '19

OARC is pleased to announce that dnsviz.net has moved to join many other tools that we support for the DNS community. DNSViz, Casey Deccio's excellent DNSSEC debugging tool, was initially developed and hosted at Sandia National Laboratories, and has been hosted most recently at Verisign. We'd like to thank them both for providing that service for many years, and Verisign for donating the hardware that DNSViz will continue to live on in the near future. We're happy to be picking up the torch! Casey continues to be the primary developer and maintainer of the application, while OARC takes on the role of hosting and operating the online service. Unfortunately, we will be without the historical functions of the tool for a little over a week while the hardware is in transit between data centers, and DNSVIZ runs on an interim platform. Full access to the historical data will be restored once the hardware is brought back online during the week of February 11th. Matt Pounsett DNS-OARC Systems Engineering

1 0