Slave won't update with BIND 8.2.3 on NT
tmadden at aspenres.com
Wed Mar 7 17:57:31 UTC 2001
On 6 Mar 2001, at 23:06, Danny Mayer wrote:
> At 09:19 PM 3/6/01, Tim Madden wrote:
> >I've just set up my first slave server, but named-xfer won't complete
> >when called by named. I can manually run named-xfer and it will pull in
> >the zone. I didn't use the default directory structure, so I wonder if
> >that's part of the problem? When named calls named-xfer, I can watch it
> >start and stop in Task Manager.
> Not related. It really doesn't care as long as it can read and write to the directory.
That's what I expected, but it's nice to hear someone else say it.
> >After each failure, named-xfer strands the following files in my C:\BIND
> >where 000044 changes, I assume, with the PID for each failed named-xfer.
> >The first two files are empty, but the xfer.ddt.xxxx file contains:
> >domain `aspenresearchgroup.com'; file `db.aspenresearchgroup.com.dom';
> >serial 0
> >domain `aspenresearchgroup.com'; ixfrfile
> >`db.aspenresearchgroup.com.dom.ixfr.tmp'; serial 0
> >tsigfile `aspenresearchgroup.com.362'
> These are standard temporary files that I created by the
> transfer. They are left behind because of the transfer failure.
Again, what I expected. What about the reference to ixfr? I know
there's an axfr and and ixfr, but I don't know the difference between
them. Could the manual copy be doing and axfr and the automatic
transfer is failing because it's doing an ixfr?
> >I've successfully used the command line:
> >c:\bind> bin\named-xfer -z aspenresearchgroup.com -f
> >db.aspenresearchgroup.com.dom -s 0 192.168.50.16
> >I've also successfully transferred the zone with -s 2001030602 (the
> >master's ser# is 2001030604)
One thing I didn't notice until after I sent my message is that the
manual transfer copies the file, but doesn't load the zone. Should
it load the zone?
> These transfers don't check the zone contents. What does
> the application event log tell you. You should see record errors
> logged there.
Nothing, really. A few informational "interogated" messages and
one warning that the directory is "world-writable". However, it does
say I'm loading BIND 8.2.3-T6B-NT Nov 5, 2000. I've just re-
downloaded and rechecked all my file dates. All my executables
are dated 1/27/01, the same as what is in the newly downloaded
.zip file, so I can only assume I'm on the released version?
> Since your master for the domain is in a private subnet I can't check, but
> I bet you have a CNAME at the root of the zone. If so, you need to get rid of it
> as it's illegal and will prevent the slave from loading the zone.
Hmm...a CNAME at the root of the zone? That I don't understand.
With the risk of being presumptuous, I've inclued the zone file from
the master at the bottom.
Also, today I've noticed an error on my private, behind the firewall
name servers (the ones we've been talking about). They both
23-Feb-2001 18:19:54.000 default: info: sysquery: findns error
(NXDOMAIN) on ns2.aspenres.com?
07-Mar-2001 08:05:39.000 default: info: sysquery: findns error
(NXDOMAIN) on ns1.aspenres.com?
ns1 and ns2 are my public name servers outside my firewall. I'm
looking for an clue now, but any suggestions welcome. I must
have something misconfigured, but I'm not sure what.
-------- db.aspenresearchgroup.com.dom --------
@ IN SOA server1.aspenresearchgroup.com. postmaster.aspenres.com. (
2001030604 ; Serial Number
3h ; refresh interval for slave ns to refresh from master
1h ; retry by slave ns if master ns is unreachable
1w ; expire from slave cache
1d ; default time-to-live in any DNS cache
IN NS server1.aspenresearchgroup.com.
IN NS intraweb.aspenresearchgroup.com.
IN A 192.168.50.16
IN MX 10 server1.aspenresearchgroup.com.
; GWS Hosts
inet-gws-2611 in a 192.168.2.1
bfinet1 in a 192.168.2.103
bfinet2 in a 192.168.2.109
bf3xtest in a 192.168.2.111
bfinet3 in a 220.127.116.11
bfinet4 in a 18.104.22.168
csinet1a in a 192.168.2.121
csinet1b in a 192.168.2.105
csinet1 in cname csinet1a
inet1 in cname csinet1b
csinet2a in a 192.168.2.122
csinet2b in a 192.168.2.102
csinet2 in cname csinet2a
inet2 in cname csinet2b
csinet3a in a 192.168.2.123
csinet3b in a 192.168.2.101
csinet3 in cname csinet3a
inet3 in cname csinet3b
csinet4a in a 192.168.2.124
csinet4b in a 192.168.2.104
csinet4 in cname csinet4a
inet4 in cname csinet4b
csinet5a in a 192.168.2.125
csinet5b in a 192.168.2.106
csinet5 in cname csinet5a
inet5 in cname csinet5b
depaul in a 192.168.2.110
www in a 22.214.171.124
ftp in cname www
arg-gws-2501 in a 126.96.36.199
Pix-outside in a 188.8.131.52
plpower in a 184.108.40.206
plpetro in a 220.127.116.11
plldn in a 18.104.22.168
pix in a 192.168.50.1
wan.gws.2610 in a 192.168.50.2
inet.gws.2611 in a 192.168.50.3
gws.2912 in a 192.168.50.4
mis1 in a 192.168.50.10
server1 in a 192.168.50.16
mx1 in cname server1
rose in cname server1
intraweb in a 192.168.50.17
news in cname intraweb
betty in a 192.168.50.18
wilma in a 192.168.50.19
Tim Madden, CNA, CCNA
Aspen Research Group, Ltd.
tmadden at aspenres.com
More information about the bind-users