Re: [MaraDNS list] MaraDNS authoritative and recursive config issue

[email protected] Wed, 24 Aug 2011 09:11:30 +0200
Newsgroups gmane.network.dns.maradns.general
Message-ID <[email protected]>
On Tue, 23 Aug 2011 18:48:29 +0200, Domenico Rotondi wrote:
> Hi,
> I'm trying to use MaraDNS-2-0-03 to solve the following problem:
> on my intranet I want to manage the mapping of a few FQDN belonging 
> to the
> "example.org" domain to IP addresses on my intranet and, at the same
> time, assure
> reolution for FQDN in other domains (including the intranet one).
> My intranet has its how DNS servers, which also manages resolutions
> for Internet
> domains.

I'm on Linux rather than Windows, but I have a setup similar to yours. 
On one box I have MaraDNS set up as an authoritative DNS for the 
home.lan zone (i.e. the intranet), and on the same box I also have 
Deadwood listening on another IP address set as recursive nameserver for 
the intranet and for the Internet.

My MaraDNS configuration file is:

ipv4_bind_addresses = "192.168.88.4"
tcp_convert_acl = "0.0.0.0/0"
tcp_convert_server = "192.168.88.4"
long_packet_ipv4 = "192.168.88.4"
chroot_dir = "/etc/maradns"
csv2 = {}
csv2["home.lan."] = "db.home.lan.conf"
verbose_level = 1

My Deadwood configuration file is:

bind_address="127.0.0.1, 192.168.88.3"
chroot_dir="/var/run/deadwood"
dns_port=53
filter_rfc1918=0
maximum_cache_elements=1024
recursive_acl="127.0.0.1/8, 192.168.88.1/16"
reject_mx=0
root_servers={}
root_servers["home.lan."]="192.168.88.4"
root_servers["."]="198.41.0.4,"
root_servers["."]+="192.228.79.201,"
root_servers["."]+="192.33.4.12,"
root_servers["."]+="128.8.10.90,"
root_servers["."]+="192.203.230.10,"
root_servers["."]+="192.5.5.241,"
root_servers["."]+="192.112.36.4,"
root_servers["."]+="128.63.2.53,"
root_servers["."]+="192.36.148.17,"
root_servers["."]+="192.58.128.30,"
root_servers["."]+="193.0.14.129,"
root_servers["."]+="199.7.83.42,"
root_servers["."]+="202.12.27.33"
tcp_listen=1
timeout_seconds=60
timeout_seconds_tcp=60
upstream_servers={}
verbose_level=3

I also have a DHCP configuration which specifies 192.168.88.3 as the 
DNS to use to all other boxes. Try adapting this configuration to your 
environment and tell us what happens.

Best regards
Sebastiano Pilla