From 35520716921c45ff7407fd05d28349a065ffa46b Mon Sep 17 00:00:00 2001 From: Chris Hofstaedtler Date: Wed, 30 May 2018 00:11:10 +0200 Subject: [PATCH] Clean up some old docstrings --- pdns/dnsbackend.hh | 2 +- pdns/nameserver.cc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pdns/dnsbackend.hh b/pdns/dnsbackend.hh index 0d35c919b5..901987f66a 100644 --- a/pdns/dnsbackend.hh +++ b/pdns/dnsbackend.hh @@ -106,7 +106,7 @@ struct TSIGKey { class DNSPacket; -//! This virtual base class defines the interface for backends for the ahudns. +//! This virtual base class defines the interface for backends for PowerDNS. /** To create a backend, inherit from this class and implement functions for all virtual methods. Methods should not throw an exception if they are sure they did not find the requested data. However, if an error occurred which prevented them temporarily from performing a lockup, they should throw a DBException, diff --git a/pdns/nameserver.cc b/pdns/nameserver.cc index ef7eef4c66..3ce54d92f6 100644 --- a/pdns/nameserver.cc +++ b/pdns/nameserver.cc @@ -61,8 +61,8 @@ extern StatBag S; A DNSBackend is an entity that returns DNSResourceRecord objects in return to explicit questions for domains with a specified QType - PowerDNS uses the UeberBackend as its DNSBackend. The UeberBackend by default has no DNSBackends within itself, those are loaded - using the pdns_control tool. This way DNSBackend implementations can be kept completely separate (but they often aren't).s + PowerDNS uses the UeberBackend, which hosts DNSBackends. By default it has no DNSBackends within itself, those are loaded + by setting --load=. This way DNSBackend implementations can be kept completely separate, but most aren't. If one or more DNSBackends are loaded, the UeberBackend fields the queries to all of them until one answers. -- 2.47.2