DOCSLIB.ORG

Powerdns Recursor Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Powerdns Recursor Documentation PowerDNS Recursor Documentation PowerDNS.COM BV Sep 30, 2021 CONTENTS 1 Introduction 1 1.1 Notable features...........................................1 1.2 Getting support............................................1 1.2.1 My information is confidential, must I send it to the mailing list, discuss it on IRC, or post it in a GitHub ticket?..................................2 1.2.2 I have a question!......................................2 1.2.3 What details should I supply?................................2 1.2.4 I found a bug!........................................2 1.2.5 I found a security issue!...................................2 1.2.6 I have a good idea for a feature!..............................2 1.3 Third party software.........................................2 1.3.1 Protozero..........................................3 2 Getting Started 5 2.1 Installation..............................................5 2.1.1 Debian-based distributions.................................5 2.1.2 Enterprise Linux......................................5 2.1.3 FreeBSD..........................................5 2.1.4 From Source........................................5 2.2 Configuring the Recursor......................................5 2.3 Using Ansible............................................6 3 Operating PowerDNS Recursor7 3.1 Logging................................................7 3.1.1 Logging to syslog......................................7 3.2 Cache Management.........................................8 3.3 Tracing Queries...........................................8 4 DNSSEC in the PowerDNS Recursor9 4.1 DNSSEC settings...........................................9 4.1.1 off .............................................9 4.1.2 process-no-validate ................................9 4.1.3 process ..........................................9 4.1.4 log-fail .........................................9 4.1.5 validate ......................................... 10 4.1.6 What, when?........................................ 10 4.2 Trust Anchor Management...................................... 10 4.2.1 Trust Anchors........................................ 10 4.2.2 Negative Trust Anchors................................... 11 5 PowerDNS Recursor Settings 13 5.1 aggressive-nsec-cache-size ............................... 13 5.2 allow-from ............................................ 13 5.3 allow-from-file ........................................ 14 5.4 any-to-tcp ............................................ 14 i 5.5 allow-trust-anchor-query ................................. 14 5.6 api-config-dir ......................................... 14 5.7 api-key .............................................. 14 5.8 api-readonly .......................................... 15 5.9 api-logfile ........................................... 15 5.10 auth-can-lower-ttl ...................................... 15 5.11 auth-zones ............................................ 15 5.12 carbon-interval ........................................ 15 5.13 carbon-namespace ....................................... 15 5.14 carbon-ourname ......................................... 16 5.15 carbon-instance ........................................ 16 5.16 carbon-server .......................................... 16 5.17 chroot ............................................... 16 5.18 client-tcp-timeout ...................................... 16 5.19 config-dir ............................................ 16 5.20 config-name ........................................... 17 5.21 cpu-map .............................................. 17 5.22 daemon ............................................... 17 5.23 dont-throttle-names ..................................... 17 5.24 dont-throttle-netmasks .................................. 18 5.25 disable-packetcache ..................................... 18 5.26 disable-syslog ......................................... 18 5.27 distribution-load-factor ................................. 18 5.28 distribution-pipe-buffer-size ............................. 19 5.29 distributor-threads ..................................... 19 5.30 dot-to-auth-names ...................................... 19 5.31 dot-to-port-853 ........................................ 19 5.32 dns64-prefix .......................................... 19 5.33 dnssec ............................................... 20 5.34 dnssec-log-bogus ....................................... 20 5.35 dont-query ............................................ 20 5.36 ecs-add-for ........................................... 20 5.37 ecs-ipv4-bits .......................................... 21 5.38 ecs-ipv4-cache-bits ..................................... 21 5.39 ecs-ipv6-bits .......................................... 21 5.40 ecs-ipv6-cache-bits ..................................... 21 5.41 ecs-ipv4-never-cache .................................... 22 5.42 ecs-ipv6-never-cache .................................... 22 5.43 ecs-minimum-ttl-override ................................. 22 5.44 ecs-cache-limit-ttl ..................................... 22 5.45 ecs-scope-zero-address .................................. 22 5.46 edns-outgoing-bufsize ................................... 23 5.47 edns-padding-from ...................................... 23 5.48 edns-padding-mode ...................................... 23 5.49 edns-padding-tag ....................................... 23 5.50 edns-subnet-whitelist ................................... 24 5.51 edns-subnet-allow-list .................................. 24 5.52 entropy-source ......................................... 24 5.53 etc-hosts-file ......................................... 24 5.54 export-etc-hosts ....................................... 24 5.55 export-etc-hosts-search-suffix ............................ 24 5.56 extended-resolution-errors ............................... 25 5.57 forward-zones .......................................... 25 5.58 forward-zones-file ...................................... 25 5.59 forward-zones-recurse ................................... 26 5.60 gettag-needs-edns-options ................................ 26 5.61 hint-file ............................................. 26 5.62 ignore-unknown-settings .................................. 26 ii 5.63 include-dir ........................................... 26 5.64 latency-statistic-size .................................. 26 5.65 local-address .......................................... 27 5.66 local-port ............................................ 27 5.67 log-timestamp .......................................... 27 5.68 non-local-bind ......................................... 27 5.69 loglevel .............................................. 27 5.70 log-common-errors ...................................... 28 5.71 log-rpz-changes ........................................ 28 5.72 logging-facility ....................................... 28 5.73 lowercase-outgoing ...................................... 28 5.74 lua-config-file ........................................ 28 5.75 lua-dns-script ......................................... 28 5.76 lua-maintenance-interval ................................. 29 5.77 max-cache-bogus-ttl ..................................... 29 5.78 max-cache-entries ...................................... 29 5.79 max-cache-ttl .......................................... 29 5.80 max-concurrent-requests-per-tcp-connection .................. 29 5.81 max-generate-steps ...................................... 30 5.82 max-mthreads .......................................... 30 5.83 max-packetcache-entries .................................. 30 5.84 max-qperq ............................................. 30 5.85 max-ns-address-qperq .................................... 30 5.86 max-negative-ttl ....................................... 31 5.87 max-recursion-depth ..................................... 31 5.88 max-tcp-clients ........................................ 31 5.89 max-tcp-per-client ...................................... 31 5.90 max-tcp-queries-per-connection ............................ 31 5.91 max-total-msec ......................................... 31 5.92 max-udp-queries-per-round ................................ 32 5.93 minimum-ttl-override .................................... 32 5.94 new-domain-tracking ..................................... 32 5.95 new-domain-log ......................................... 32 5.96 new-domain-lookup ...................................... 33 5.97 new-domain-db-size ...................................... 33 5.98 new-domain-history-dir .................................. 33 5.99 new-domain-whitelist .................................... 33 5.100 new-domain-ignore-list .................................. 33 5.101 new-domain-pb-tag ...................................... 34 5.102 network-timeout ........................................ 34 5.103 non-resolving-ns-max-fails ............................... 34 5.104 non-resolving-ns-max-throttle-time ......................... 34 5.105 nothing-below-nxdomain .................................. 34 5.106 nsec3-max-iterations .................................... 35 5.107 packetcache-ttl ........................................ 35 5.108 packetcache-servfail-ttl ................................. 35 5.109 pdns-distributes-queries ................................. 35 5.110 protobuf-use-kernel-timestamp ............................. 36 5.111 proxy-protocol-from ..................................... 36 5.112 proxy-protocol-maximum-size .............................
Load more

Recommended publications
  • Ispconfig 3 Manual]
    [ISPConfig 3 Manual] ISPConfig 3 Manual Version 1.0 for ISPConfig 3.0.3 Author: Falko Timme <[email protected]> Last edited 09/30/2010 1 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH. You may keep backup copies of the manual in digital or printed form for your personal use. All rights reserved. This copy was issued to: Thomas CARTER - [email protected] - Date: 2010-11-20 [ISPConfig 3 Manual] ISPConfig 3 is an open source hosting control panel for Linux and is capable of managing multiple servers from one control panel. ISPConfig 3 is licensed under BSD license. Managed Services and Features • Manage one or more servers from one control panel (multiserver management) • Different permission levels (administrators, resellers and clients) + email user level provided by a roundcube plugin for ISPConfig • Httpd (virtual hosts, domain- and IP-based) • FTP, SFTP, SCP • WebDAV • DNS (A, AAAA, ALIAS, CNAME, HINFO, MX, NS, PTR, RP, SRV, TXT records) • POP3, IMAP • Email autoresponder • Server-based mail filtering • Advanced email spamfilter and antivirus filter • MySQL client-databases • Webalizer and/or AWStats statistics • Harddisk quota • Mail quota • Traffic limits and statistics • IP addresses 2 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH.
    [Show full text]
  • To the Members of the Senate Judiciary Committee: We, The
    To the members of the Senate Judiciary Committee: We, the undersigned, have played various parts in building a network called the Internet. We wrote and debugged the software; we defined the standards and protocols that talk over that network. Many of us invented parts of it. We're just a little proud of the social and economic benefits that our project, the Internet, has brought with it. We are writing to oppose the Committee's proposed new Internet censorship and copyright bill. If enacted, this legislation will risk fragmenting the Internet's global domain name system (DNS ), create an environment of tremendous fear and uncertainty for technological innovation, and seriously harm the credibility of the United States in its role as a steward of key Internet infrastructure. In exchange for this, the bill will introduce censorship that will simultaneously be circumvented by deliberate infringers while hampering innocent parties' ability to communicate. All censorship schemes impact speech beyond the category they were intended to restrict, but this bill will be particularly egregious in that regard because it causes entire domains to vanish from the Web, not just infringing pages or files. Worse, an incredible range of useful, law-abiding sites can be blacklisted under this bill. These problems will be enough to ensure that alternative name-lookup infrastructures will come into widespread use, outside the control of US service providers but easily used by American citizens. Errors and divergences will appear between these new services and the current global DNS, and contradictory addresses will confuse browsers and frustrate the people using them.
    [Show full text]
  • Domain Name Server Comparison
    DomainNameServerComparison: BIND8vs.BIND9vs.djbdnsvs.??? BradKnowles SeniorConsultantforSnow,BV [email protected] http://www.shub-internet.org/brad/papers/dnscomparison/ Entirecontentscopyright©2003byBradKnowles,allrightsreserved Overview • Meta Information • TLD Survey Results • Software – Installation – Features – Performance • Conclusions 2003-01-28 Copyright©2003byBradKnowles 2 MetaInformation • Hardware Used • Software Used • Methodology 2003-01-28 Copyright©2003byBradKnowles 3 HardwareUsed • TLD Survey – OS: BSD/OS 4.2 – CPU: Pentium III – RAM: 512MB real, 1.0GB virtual 2003-01-28 Copyright©2003byBradKnowles 4 HardwareUsed • Performance Testing – Compaq Armada 4131T Laptop • OS: FreeBSD 4.6.2-RELEASE • CPU: Pentium 133 • RAM: 48MB real, 384MB virtual • NICs: Asanté FriendlyNET AL1011 “Prism2” 802.11b WiFi PC Card & Linksys EtherFast 10/100 PC Card (PCM100) • HD: 10GB IBM Travelstar 20GN – 4200 RPM – 12ms avg. seek 2003-01-28 Copyright©2003byBradKnowles 5 HardwareUsed: PerformanceTesting Image copyright © 2001 Sunset Computer Services, Inc. All Rights Reserved. 2003-01-28 Copyright©2003byBradKnowles 6 SoftwareUsed • ISC – BIND 8.3.3-REL – BIND 9.2.2rc1 • djbdns 1.05 – daemontools 0.76 – ucpsi-tcp 0.88 – tinydns-bent 1.1 • nsd 1.02b1 • Nominum – ANS (Authoritative Name Server) 2.0.1-1eval – CNS (Caching Name Server) 1.1.0b1 • PowerDNS 2.9.4 2003-01-28 Copyright©2003byBradKnowles 7 SomeSoftwareConsidered • QuickDNS (authoritative) – See <http://www.menandmice.com/2000/2600_isp_dns_solution.html> • Aimed at small-to-medium size businesses,
    [Show full text]
  • Sirdom. Sistema Para La Gestión Del Servicio De Resolución De Nombres De Dominios
    Revista de investigación Editada por Área de Innovación y Desarrollo, S.L. Envío: 27-01-2013 Aceptación: 30-01-2013 Publicación: 19-02-2013 SIRDOM. SISTEMA PARA LA GESTIÓN DEL SERVICIO DE RESOLUCIÓN DE NOMBRES DE DOMINIOS SIRDOM. MANAGEMENT SYSTEM FOR THE RESOLUTION NAMES DOMAINS SERVICE. Yoedusvany Hernández Mendoza1 Yordanis Arencibia López2 Yankier Crespo González3 1. Máster, Ingeniero Informático. Profesor del Departamento de Redes, UNICA. 2. Máster, Ingeniero Informático. Profesor del Departamento de Redes, UNICA. 3. Máster, Ingeniero Informático. Profesor del Departamento de Redes, UNICA. RESUMEN Este artículo presenta un estudio del comportamiento del servicio DNS, su funcionamiento, herramientas y por último se propone un sistema informático que permite configurar y gestionar dicho servicio a través de una serie de prestaciones y facilidades que las aplicaciones actuales no posibilitan. Este sistema permitirá gestionar el servicio de resolución de nombres de dominio sobre BIND en su versión 9. ABSTRACT This paper presents a study of the behavior of DNS, its operating principle, tools and finally proposes a computer system to configure and manage this service through a number of benefits and facilities that do not allow current applications. This system will manage the service of domain name resolution on BIND version 9. PALABRAS CLAVE Bind, DNS, dominio, resolución, sistema. KEYWORDS Bind, DNS, domain, resolution, system. SIRDOM. SISTEMA PARA LA GESTIÓN DEL SERVICIO DE RESOLUCIÓN DE NOMBRES DE DOMINIOS DE NOMBRES DE RESOLUCIÓN DE SERVICIO DEL GESTIÓN LA PARA SISTEMA SIRDOM. 2 INTRODUCCIÓN Las diferentes instituciones y organizaciones, siendo los centros educacionales unos de los principales, han tenido que cambiar sus esquemas tradicionales para adaptarse a la actual era de la información.
    [Show full text]
  • Powerdns Offerings ­ Version Current As of November 2012 ● Remotely Pollable Statistics for Real Time Graphing ● High Performance ● SNMP Statistics Bridge (Read Only)
    Products, Features & Services PowerDNS PowerDNS, founded in the late 1990s, is a premier supplier of DNS software, services and support. Deployed throughout the world with some of the most demanding users of DNS, we pride ourselves on quality software and the very best support available. PowerDNS customers include leading telecommunications service providers, large scale integrators, content distribution networks, cable networks / multi service operators and Fortune 500 software companies. In various important markets, like Scandinavia, Germany and The Netherlands, PowerDNS is the number one supplier of nameserver software. PowerDNS is based in The Netherlands, Europe and is privately held. Products Authoritative Server The PowerDNS Authoritative Server is the only solution that enables authoritative DNS service from all major databases, including but not limited to MySQL, PostgreSQL, SQLite3, Oracle, Sybase, Microsoft SQL Server, LDAP and plain text files. DNS answers can also be fully scripted using a variety of (scripting) languages like for example Lua, Java, Perl, Python, Ruby, C and C++. Such scripting can be used for dynamic redirection, (spam)filtering or real time intervention. In addition, the PowerDNS Authoritative Server is the leading DNSSEC implementation, hosting the majority of all DNSSEC domains worldwide. The Authoritative Server hosts at least 30% of all domain names in Europe, and around 90% of all DNSSEC domains in Europe. Recursor The PowerDNS Recursor is a high­end, high­performance resolving name server which powers the DNS resolution of at least a hundred million subscribers. Utilizing multiple processors and supporting the same powerful scripting ability of the Authoritative Server, the Recursor delivers top performance while retaining the flexibility modern DNS deployments require.
    [Show full text]
  • Självständigt Arbete På Grundnivå
    Självständigt arbete på grundnivå Independent degree project - first cycle Datateknik Computer Engineering Master's thesis Hantering av nätverkscache i DNS Two ye Hans Lindqvist i MITTUNIVERSITETET Avdelningen för informationssystem och -teknologi (IST) Examinator: Ulf Jennehag, [email protected] Handledare: Johannes Lindén, [email protected] Författare: Hans Lindqvist, [email protected] Utbildningsprogram: Datateknik, 180 hp Huvudområde: Datateknik Termin, år: VT, 2019 ii Hantering av nätverkscache i DNS Hans Lindqvist 2019-06-13 Sammanfattning Domännamnsystemet, DNS, utgör en fundamental del av användbarheten för Internet, men dess cachefunktion utmanas av adressers ökande storlek, antal och automatisering. Parallellt råder begränsad minneskapacitet hos vissa enheter i Internets utkant mot Internet of Things. Studien har tittat närmare på nutida behov av namnuppslagning och har då betraktat hur DNS påverkats av IPv6- adressutbredning, mobila enheter, innehållsleveransnätverk och webbläsarfunktioner. Undersökningen har i två fritt tillgängliga serverprogramvaror för DNS-uppslag sökt efter den optimala hanteringen av cache hos begränsade enheter i, eller på gränsen till, Sakernas Internet. Med hjälp av tillgången till öppen källkod för programmen, Unbound och PowerDNS Recursor, har dess respektive strukturer tolkats för att uppskatta och jämföra minnesbehov. Därefter har en simulering gjorts i en laborativ miljö med fiktiva DNS-data av verklighetstrogen karaktär för att mäta den faktiska förbrukningen av minne på DNS-serverns process. Vid simuleringen undveks att individuellt anpassa programmens inställningar, att blanda in data för DNSSEC, samt att införa minnesbegränsningar i testmiljön. Undersökningen av källkod beräknade att Unbound var mer optimalt för posttyperna A+AAAA medan PowerDNS Recursor var effektivare för posttypen PTR. För båda posttyperna som helhet visade mätningarna i simuleringen att Unbound kunde lagra DNS-data tätare än PowerDNS Recursor.
    [Show full text]
  • Build Securely a DNS Sinkhole Step-By-Step Powered by Slackware Linux
    Guy Bruneau – [email protected] Twitter : @GuyBruneau Build Securely a DNS Sinkhole Step-by-Step Powered by Slackware Linux By Guy Bruneau, GSE Version 2.1 – 23 October 2016 1. DNS Sinkhole Overview............................................................................................. 2 1.1 Installation, Configuration and Partitioning the Drive ......................................... 2 1.1.1 DNS Sinkhole Server Installation ................................................................. 2 1.1.2 Install the Software ....................................................................................... 3 1.2 Sinkhole Configuration ........................................................................................ 4 1.2.1 Configure Bind as DNS Sinkhole ................................................................. 4 1.2.2 Testing the Bind Service ............................................................................... 6 1.3 PowerDNS DNS Sinkhole Setup ......................................................................... 6 1.3.1 PowerDNS Forwarding Configuration ......................................................... 7 1.3.2 Testing the PowerDNS Service .................................................................... 7 2. DNS Sinkhole Web Interface ...................................................................................... 8 2.1 Configure Local Sinkhole Address(es) ................................................................ 8 2.2 Populating Site Exclusion List ..........................................................................
    [Show full text]
  • XML Prague 2019
    XML Prague 2019 Conference Proceedings University of Economics, Prague Prague, Czech Republic February 7–9, 2019 XML Prague 2019 – Conference Proceedings Copyright © 2019 Jiří Kosek ISBN 978-80-906259-6-9 (pdf) ISBN 978-80-906259-7-6 (ePub) Table of Contents General Information ..................................................................................................... vii Sponsors .......................................................................................................................... ix Preface .............................................................................................................................. xi Task Abstraction for XPath Derived Languages – Debbie Lockett and Adam Retter ........................................................................................ 1 A novel approach to XSLT-based Schematron validation – David Maus .............. 57 Authoring DSLs in Spreadsheets Using XML Technologies – Alan Painter ......... 67 How to configure an editor – Martin Middel ........................................................... 103 Discover the Power of SQF – Octavian Nadolu and Nico Kutscherauer .................. 117 Tagdiff: a diffing tool for highlighting differences in text-oriented XML – Cyril Briquet .................................................................................................................. 143 Merge and Graft: Two Twins That Need To Grow Apart – Robin La Fontaine and Nigel Whitaker ........................................................................
    [Show full text]
  • Using Dns to Protect Clients from Malicious Domains
    Institute for Development and Research in Banking Technology A Project Report on USING DNS TO PROTECT CLIENTS FROM MALICIOUS DOMAINS Submitted by M.L.V.L Akhil Vishnu 3rd year B.Tech, Computer Science and Engineering Indian Institute of Technology (ISM) Dhanbad. Guide Dr. V. Radha Assistant professor IDRBT, Hyderabad. 1 | P a g e ACKNOWLEDGEMENT I would like to express my gratitude to the Institute for Development and Research in Banking Technology (IDRBT) under the guidance of Dr. V. Radha, Assistant Professor, IDRBT, Hyderabad. I would not hesitate to add that this short stint in IDRBT has added a different facet to my life as this is a unique organization being a combination of academics, research, technology, communication service, crucial application etc. and at the same time performing roles as an arm of regulation, spread of technology, and facilitator for implementing technology in banking and non-banking system. I am extremely grateful to Dr. V.Radha for her advice, innovative suggestions and supervision. I thank her for introducing me to different aspects of “CYBER SECURITY AND DOMAIN NAME SYSTEMS”. I am thankful for IDRBT for providing such an amazing platform to work on real application oriented research. I would like to give special thanks to Mrs. Varsha Srivastava, Administrative Executive, IDRBT, Hyderabad for providing resource and motivation in carrying out this project. Finally, I thank one and all who made this project successful either directly or indirectly. M.L.V.L Akhil Vishnu 3rd year B.Tech, Computer Science and Engineering, Indian Institute of Technology (ISM) Dhanbad. 2 | P a g e CERTIFICATE This is to certify that Mr.
    [Show full text]
  • Powerdns Manual
    PowerDNS manual PowerDNS BV [email protected] PowerDNS manual by Published v2.9.19 $Date: 2005-10-29 17:45:03 +0200 (Sat, 29 Oct 2005) $ It is a book about a Spanish guy called Manual. You should read it. -- Dilbert Table of Contents 1. The PowerDNS dynamic nameserver ..................................................................................................1 1.1. Function & design of PDNS .......................................................................................................1 1.2. About this document ...................................................................................................................1 1.3. Release notes...............................................................................................................................1 1.3.1. Version 2.9.19.................................................................................................................2 1.3.2. Version 2.9.18.................................................................................................................4 1.3.3. Version 2.9.17.................................................................................................................7 1.3.4. Version 2.9.16.................................................................................................................8 1.3.5. Version 2.9.15.................................................................................................................9 1.3.6. Version 2.9.14...............................................................................................................10
    [Show full text]
  • Creating a Patch and Vulnerability Management Program
    Archived NIST Technical Series Publication The attached publication has been archived (withdrawn), and is provided solely for historical purposes. It may have been superseded by another publication (indicated below). Archived Publication Series/Number: NIST Special Publication 800-40 Version 2.0 Title: Creating a Patch and Vulnerability Management Program Publication Date(s): November 2005 Withdrawal Date: July 2013 Withdrawal Note: SP 800-40 is superseded by the publication of SP 800-40 Revision 3 (July 2013). Superseding Publication(s) The attached publication has been superseded by the following publication(s): Series/Number: NIST Special Publication 800-40 Revision 3 Title: Guide to Enterprise Patch Management Technologies Author(s): Murugiah Souppaya, Karen Scarfone Publication Date(s): July 2013 URL/DOI: http://dx.doi.org/10.6028/NIST.SP.800-40r3 Additional Information (if applicable) Contact: Computer Security Division (Information Technology Lab) Latest revision of the SP 800-40 Revision 3 (as of June 19, 2015) attached publication: Related information: http://csrc.nist.gov/ Withdrawal SP 800-40 Version 2 provides basic guidance on establishing patch announcement (link): management programs, and guidance to organizations with legacy needs. Date updated: June Ϯϯ, 2015 Special Publication 800-40 Version 2.0 Creating a Patch and Vulnerability Management Program Recommendations of the National Institute of Standards and Technology (NIST) Peter Mell Tiffany Bergeron David Henning NIST Special Publication 800-40 Creating a Patch and Vulnerability Version 2.0 Management Program Recommendations of the National Institute of Standards and Technology Peter Mell Tiffany Bergeron David Henning C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 November 2005 U.S.
    [Show full text]
  • Improving Robustness of DNS to Software Vulnerabilities
    " ! " # $ " fail-stop failures, where a system stops when it encounters The ability to forward packets on the Internet is highly in- an error, Byzantine errors include the more arbitrary class tertwined with the availability and robustness of the Do- of faults where a system can violate protocol. For exam- main Name System (DNS) infrastructure. Unfortunately, ple, software errors in DNS implementations lead to bogus the DNS suffers from a wide variety of problems arising queries [27] and vulnerabilities, which can be exploited by from implementation errors, including vulnerabilities, bogus attackers to gain access to and control DNS servers. These queries, and proneness to attack. In this work, we present a problems are particularly serious for DNS – while the root preliminary design and early prototype implementation of a of the DNS hierarchy is highly physically redundant to avoid system that leverages diversified replication to increase toler- hardware failures, it is not software redundant, and hence ance of DNS to implementation errors. Our design leverages multiple servers can be taken down with the same attack. software diversity by running multiple redundant copies of For example, while there are 13 geographically distributed software in parallel, and leverages data diversity by send- DNS root clusters, each comprised of hundreds of servers, ing redundant requests to multiple servers. Using traces of they only run two distinct DNS software implementations: DNS queries, we demonstrate our design can keep up with BIND and NSD (see [8] and references therein). While co- the loads of a large university’s DNS traffic, while improving ordinated attacks to DoS these servers are hard, the fact resilience of DNS.
    [Show full text]