CentOS - Mar 2009 - How to setup a "secondary DNS server" pulling zones from Win2k3?

Hello,

we have a mixed environment at work: CentOS + Win2003 servers.
The Win2k3 part contains: AD, DNS (inlc. dyndns), DHCP, DFS, Exchange.
The CentOS part: NIS passwords + also a DNS server.

So currently we have to update the Linux DNS server
zone infos by hand: I export a text file from
Windows DNS server and then edit it around using vim.

On the Windows side however it's easy for me to setup
additional DNS servers at other machines: I just configure
them as "secondary" and they pull zone infos automatically.

I wonder if there is a way to setup such a "secondary" DNS
server under CentOS as well?

And no, I'm not asking about how to setup a DNS-forwarder.
(Because I want the Linux server to pull and maintain zone infos
automatically and to work even if Windows-counterpart is down.)

Regards
Alex

I found this useful...

http://technet.microsoft.com/en-us/library/dd316373.aspx

On Thu, Mar 5, 2009 at 6:22 PM, Alexander Farber <alexander.farber at
gmail.com
> wrote:
> Hello,
>
> we have a mixed environment at work: CentOS + Win2003 servers.
> The Win2k3 part contains: AD, DNS (inlc. dyndns), DHCP, DFS, Exchange.
> The CentOS part: NIS passwords + also a DNS server.
>
> So currently we have to update the Linux DNS server
> zone infos by hand: I export a text file from
> Windows DNS server and then edit it around using vim.
>
> On the Windows side however it's easy for me to setup
> additional DNS servers at other machines: I just configure
> them as "secondary" and they pull zone infos automatically.
>
> I wonder if there is a way to setup such a "secondary" DNS
> server under CentOS as well?
>
> And no, I'm not asking about how to setup a DNS-forwarder.
> (Because I want the Linux server to pull and maintain zone infos
> automatically and to work even if Windows-counterpart is down.)
>
> Regards
> Alex
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20090305/8f86eff4/attachment-0004.html>

Alexander Farber wrote:
> Hello,
> 
> we have a mixed environment at work: CentOS + Win2003 servers.
> The Win2k3 part contains: AD, DNS (inlc. dyndns), DHCP, DFS, Exchange.
> The CentOS part: NIS passwords + also a DNS server.
> 
> So currently we have to update the Linux DNS server
> zone infos by hand: I export a text file from
> Windows DNS server and then edit it around using vim.
> 
> On the Windows side however it's easy for me to setup
> additional DNS servers at other machines: I just configure
> them as "secondary" and they pull zone infos automatically.
> 
> I wonder if there is a way to setup such a "secondary" DNS
> server under CentOS as well?
> 
> And no, I'm not asking about how to setup a DNS-forwarder.
> (Because I want the Linux server to pull and maintain zone infos
> automatically and to work even if Windows-counterpart is down.)
You can specify multiple forwarders if you have more than one server 
already set up the way you want.  Named will find one that works and 
cache the results locally for its time to live.  Once you have a couple 
of robust boxes configured it is easier to do that on the rest than to 
deal with local zones everywhere.

Or, if you really want to act as a secondary, just make a zone type of 
'slave' and specify the masters and a file to hold the zone info.  You 
will also have to permit the transfer to this host on the windows server 
side.

-- 
   Les Mikesell
    lesmikesell at gmail.com

Hello,

On Thu, Mar 5, 2009 at 12:44 PM, Brian McKerr <bmckerr at gmail.com>
wrote:
> http://technet.microsoft.com/en-us/library/dd316373.aspx
thank you, I have the forward zones replicated from the
prim. DNS hosted at our Windows DC fine with this config:

# cat /etc/*release
CentOS release 5.2 (Final)

# rpm -qa|grep bind
bind-libs-9.3.4-6.0.3.P1.el5_2
bind-9.3.4-6.0.3.P1.el5_2
ypbind-1.19-8.el5
bind-utils-9.3.4-6.0.3.P1.el5_2
bind-chroot-9.3.4-6.0.3.P1.el5_2

# cat /var/named/chroot/etc/named.conf
options { directory "/var/named"; };

zone "internal.mycompany.com" IN {
        type slave;
        file "slaves/internal.mycompany.com";
        masters { 10.121.42.40 port 53;};
        check-names ignore;
};

zone "42.121.10.in-addr.arpa" IN {
        type slave;
        file "slaves/10.121.42";
        masters { 10.121.42.40 port 53;};
        check-names ignore;
};

include "/etc/rndc.key";

But the replication of the reverse zone doesn't work yet - I get errors:

named[30219]: zone 42.121.10.in-addr.arpa/IN: refresh:
unexpected rcode (NXDOMAIN) from master 10.121.42.40#53 (source 0.0.0.0#0)

Maybe I need to use some other name there?

I'm reading out on "dig" tool currently, trying to find out which
zone names are served by the Windows prim. DNS...

Regards
Alex