named slave problem
Patrick Nelson
pnelson at neatech.com
Sat Jan 24 22:22:43 UTC 2004
On Sat, 2004-01-24 at 14:03, Mike Klinke wrote:
> On Saturday 24 January 2004 15:21, Patrick Nelson wrote:
> > FC1
> > bind-chroot-9.2.2.P3-9
> > bind-utils-9.2.2.P3-9
> > bind-9.2.2.P3-9
> > redhat-config-bind-2.0.0-18
> > Everything up to date with Yum
> >
> > This is the same on the master (newmaster) and the slave (newslave)
> > systems. The newmaster is working great. I setup the newslave
> > exactly like the newmaster except for the entries in named.conf
> > that designate a zone a slave to newmaster.
> >
> > If I point the named.conf slave entry to one of my old named
> > servers (oldmaster) the newslave works great as the secondary dns.
> > However if I point the newslave to the newmaster I get the
> > following error:
> >
> > <date> <sys> named[15137]: zone test.com/IN: refresh: failure
> > trying master <local ip of newmaster>#53: timed out
> >
> > I can't seem to figure out why the newmaster will not allow a
> > connection for the newslave. Can anyone point me to anything I can
> > try?
>
> Off the cuff ...
>
> Do you have a firewall in the path; master, slave, or in-between? Both
> 53/udp an 53/tcp will need to be open for transfers to work.
Hoped that maybe I overlooked that but from a iptables listing on both
newmaster and newslave:
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
I practically copied the configuration over from oldmaster and and old
slave (oldslave) to newmaster and newslave. Is there some other
configuration that I missed? Oh on the oldmaster and oldslave I run:
RH72 (I run them in a chroot jail)
bindconf-1.6.1-1
bind-utils-9.2.1-1.7x.2
bind-devel-9.2.1-1.7x.2
bind-9.2.1-1.7x.2
This is driving me nuts... Any other suggestions would be much
appreciated.
More information about the fedora-list
mailing list