Move DNS handling to a module

data/modules.example.conf

@@ -16,6 +16,52 @@
  */
 module { name = "help" }
 
+/*
+ * m_dns
+ *
+ * Adds support for the DNS protocol. By itself this module does nothing useful,
+ * but other modules such as m_dnsbl and os_dns require this.
+ */
+#module { name = "m_dns" }
+dns
+{
+	/* 
+	 * The nameserver to use for resolving hostnames, must be an IP or a resolver configuration file.
+	 * The below should work fine on all unix like systems. Windows users will have to find their nameservers
+	 * from ipconfig /all and put the IP here
+	 */
+	nameserver = "/etc/resolv.conf"
+	#nameserver = "127.0.0.1"
+
+	/*
+	 * How long to wait in seconds before a DNS query has timed out
+	 */
+	timeout = 5
+
+	/* Only edit below if you are expecting to use os_dns or otherwise answer DNS queries. */
+
+	/*
+	 * The IP and port services use to listen for DNS queries.
+	 * Note that ports less than 1024 are privileged on UNIX/Linux systems, and
+	 * require Anope to be started as root. If you do this, it is recommended you
+	 * set options:user and options:group so Anope can change users after binding
+	 * to this port.
+	 */
+	ip = "0.0.0.0"
+	port = 53
+
+	/*
+	 * SOA record information.
+	 */
+	 admin = "admin@example.com"
+	 /* This should be the names of the public facing nameserver serving the records */
+	 nameservers = "ns1.example.com ns2.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
+}
+
 /*
  * m_dnsbl
  *
@@ -23,7 +69,7 @@ module { name = "help" }
  * is found on the blacklist they will be immediately banned. This is a crucial module
  * to prevent bot attacks.
  */
-module { name = "m_dnsbl" }
+#module { name = "m_dnsbl" }
 m_dnsbl
 {
 	/*