Difference between revisions of "2.0/Modules/os dns"

/*
 * os_dns
 *
 * Provides the command operserv/dns.
 *
 * This module requires that m_dns is loaded.
 *
 * This module allows controlling a DNS zone. This is useful for
 * controlling what servers users are placed on for load balancing,
 * and to automatically remove split servers.
 *
 * To use this module you must set a nameserver record for services
 * so that DNS queries go to services.
 *
 * 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 { max-refresh-time 60; };
 * zone "irc.example.com" IN {
 *   type slave;
 *   masters { 127.0.0.1 port 5353; };
 * };
 *
 * 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"
 
        /* TTL for records. This should be very low if your records change often. */
        ttl = 1m
 
        /* If a server drops this many users the server is automatically removed from the DNS zone.
         * This directive is optional.
         */
        user_drop_mark = 50
 
        /* The time used for user_drop_mark. */
        user_drop_time = 1m
 
        /* When a server is removed from the zone for dropping users, it is readded after this time.
         * This directive is optional.
         */
        user_drop_readd_time = 5m
 
        /* If set, when a server splits, it is automatically removed from the zone. */
        remove_split_servers = yes
 
        /* If set, when a server connects to the network, it will be automatically added to
         * the zone if it is a known server.
         */
        readd_connected_servers = no
}
#command { service = "OperServ"; name = "DNS"; command = "operserv/dns"; permission = "operserv/dns"; }