Session
Schedule FOSDEM 2020
DNS

HashDNS and FQDNDHCP

IPv6 DNS configuration made easy
H.1309 (Van Rijn)
Renzo Davoli
Would you like a DNS server for IPv6 where adding a new node is as simple as typing in its name? If the answer is yes, try HashDNS.
IPv6 autoconfiguration methods can give addresses to interfaces but do not provide any means of configuring the DNS. So autoconfiguration is suitable for clients. If a host has to act as a server, it must have a fully qualified domain name and the DNS service has to map its name to its IP address. In the Internet of Thread scenario, the number of network nodes can be orders of magnitude higher than before, as each process or thread can be a node. This idea of hash based IPv6 addresses is a viable solution to the problem to manage the DNS resolution in IoTh environments. The host part of an IPv6 address can be computed as the result of a hash function computer on the fully qualified domain name. In this way it is possible to write a DNS server able to resolve the addresses of any hostname in a sub-domain provided the network prefix of that sub-domain. The installation of a new node of the network (computer, namespace, IoTh process) is as simple as providing it with its IPv6 address (the one obtained by concatenating the network prefix and the host address computed by the hash function). There is no need to change the configuration of the DNS. Actually the installation of a new node (or its renaming) is even simpler than that. The host can use a DHCP service designed to get the right address from the DNS server given its fully qualified domain name. So a system administrator has nothing to do more than assigning the new node its name. (They have just to baptize the new node)

Additional information

Type devroom

More sessions

2/1/20
DNS
H.1309 (Van Rijn)
Welcome to the DNS DevRoom
2/1/20
DNS
Graham Hayes
H.1309 (Van Rijn)
All major clouds have integrated DNS management these days, and OpenStack is one of them. We will run through the OpenStack DNS (Designate) project - how it works, why we laid it out the way we did, how you can use it, and how other OpenStack components can leverage it.
2/1/20
DNS
Erwin Hoffmann (feh)
H.1309 (Van Rijn)
The fehQlibs and djbdnscurve6 provide both a DNS library which support IPv6 LLU addresses. The inclusion and use of IPv6 LLU addresses is discussed. While the typical Unix /etc/resolv.conf is applied system-wide and the Microsoft Window's pendent works interface-dependent, here application specific DNS settings can be used.
2/1/20
DNS
Stéphane Bortzmeyer
H.1309 (Van Rijn)
Of course, encrypting DNS is necessary for privacy and security, like for every other Internet protocol. That's why DoT and DoH deployment is very important, so that users could safely go to a resolver they trust. Now, it is time to assert the technical compliance and performance of these trusted resolvers. We will talk about the things that could and should be tested against DoT and DoH servers and how to implement it. We will then discuss performance measurements, specially with the ...
2/1/20
DNS
Ondřej Surý
H.1309 (Van Rijn)
BIND 9 consists of a huge and old codebase. In this talk, I would like you to show all the available tools that we use on regular basis to improve, refactor and make the BIND 9 code safer. I'll show the examples of various Google/LLVM Sanitizers, cppcheck, LLVM scan-build and semantic patching using coccinelle.
2/1/20
DNS
Florian Obser
H.1309 (Van Rijn)
DNS is easy. You type fosdem.org in your browser's address bar, hit enter and you will be greeted by your favorite open-source event's start page. Actually...
2/1/20
DNS
Leo Vandewoestijne
H.1309 (Van Rijn)
another approach in automating maintenance