home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.domains:719 comp.sys.sun.admin:8586
- Newsgroups: comp.protocols.tcp-ip.domains,comp.sys.sun.admin
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!saimiri.primate.wisc.edu!ames!pacbell.com!iggy.GW.Vitalink.COM!nocsun.NOC.Vitalink.COM!netarch!rc
- From: rc@netarch.com (Ran-Chi Huang)
- Subject: Re: xfer error on secondary at zone transfer time.
- Message-ID: <1992Nov23.071644.14538@netarch.com>
- Organization: Network Architecture Consulting
- References: <1992Nov20.191516.27641@homebase.vistachrome.com>
- Date: Mon, 23 Nov 1992 07:16:44 GMT
- Lines: 15
-
- In article <1992Nov20.191516.27641@homebase.vistachrome.com> eric@homebase.vistachrome.com (Eric Brunson) writes:
- >I have had a DNS primary running for a few months, and have recently
- >set up a secondary. The secondary seems to have transfered the zones
- >correctly from the primary (since the backup files are all there in
- >/var/named), but every 600 seconds I get a syslog message that states:
- >
- >pod1server named[3737]: xfer returned 255
-
- I have encountered this problem previously. The problem is a misconfigured
- secondary nameserver. This is most likely in the /etc/named.boot file on
- the secondary server.
- --
- --
- Ran-Chi Huang rc@netarch.com
- Network Architecture Consulting., Fremont, CA netarch!rc
-