From 1057fa842144e84563ddd887beaeaebe8c4f8a47 Mon Sep 17 00:00:00 2001 From: Adam Date: Wed, 24 Oct 2012 19:32:26 -0400 Subject: BIND's forward ability did not work as I expected because it will not forward non recursive queries. So, added support for SOA, NS, and AXFR requests. --- data/example.conf | 15 ++++++++++++++- data/operserv.example.conf | 22 +++++++++++----------- 2 files changed, 25 insertions(+), 12 deletions(-) (limited to 'data') diff --git a/data/example.conf b/data/example.conf index 8330eeb78..54bf09f2a 100644 --- a/data/example.conf +++ b/data/example.conf @@ -1037,7 +1037,7 @@ mail * [OPTIONAL] DNS Config * * This section is used to configure DNS. - * At this time DNS is only used by a few modules (m_dnsbl) + * At this time DNS is only used by a few modules (m_dnsbl and os_dns) * and is not required by the core to function. */ dns @@ -1055,6 +1055,8 @@ dns */ timeout = 5 + /* Only edit below if you are expecting to use os_dns */ + /* * The IP and port services use to listen for DNS queries. * Note that ports less than 1024 are privileged on UNIX/Linux systems, and @@ -1064,6 +1066,17 @@ dns */ ip = "0.0.0.0" port = 53 + + /* + * SOA record information. + */ + admin = "admin@example.com" + /* This should be the name of the public facing nameserver serving the records */ + primary_nameserver = "ns1.example.com" + /* The time slave servers are allowed to cache. This should be reasonably low + * if you want your records to be updated without much delay. + */ + refresh = 3600 } /* diff --git a/data/operserv.example.conf b/data/operserv.example.conf index 167d13c04..8a887c5ea 100644 --- a/data/operserv.example.conf +++ b/data/operserv.example.conf @@ -366,21 +366,21 @@ defcon * To use this module you must set a nameserver record for services * so that DNS queries go to services. * - * We recommend you use something similar to BIND's query forwarding - * ability to hide service's IP, provide query caching, and provide - * better fault tolerance. To do this, configure BIND similar to: + * Alternatively, you may use a slave DNS server to hide service's IP, + * provide query caching, and provide better fault tolerance. + * + * To do this using BIND, configure similar to: * - * options { - * dnssec-enable no; - * dnssec-validation no; - * }; * zone "irc.example.com" IN { - * type forward; - * forward first; - * forwarders { 10.0.0.1 port 5353; }; # Where this is the IP and dns:port of services + * type slave; + * masters { 127.0.0.1 port 5353; }; * }; * - * And then set a NS record for irc.example.com. to BIND. + * Where 127.0.0.1:5353 is the IP and port services are listening on. + * We recommend you externally firewall both UDP and TCP to the port + * Anope is listening on. + * + * Finally set a NS record for irc.example.com. to BIND or services. */ #module { name = "os_dns" } #command { service = "OperServ"; name = "DNS"; command = "operserv/dns"; permission = "operserv/dns"; } -- cgit