Errors loading zones in 8.2.3

[Kevin Darcy]

Look back in the list archives around December 18 through 21, 2000. Someone

else (Eelko de Groot) was having a similar problem with BIND on SCO. Mark
Andrews suggested removing "-K pic" from the Makefiles and recompiling.
Apparently that worked around the problem. This is an SCO issue (broken
isprint()). It's possible that maybe SCO has a fix for the problem now and
so
the workaround is no longer necessary...


- Kevin

news at mtcnet.net wrote:

> Running BIND-8.2.3 on SCO OpenServer 5.0.5, I receive the following
> errors in my syslog file.
> (Note: all information was changed to provide anonymity for the server
> having these problems.)
>
> Feb 27 13:20:06 myhost named[9152]: starting
> (/usr/local/named/named.conf).
>   named 8.2.3-REL Mon Feb 12 15:42:34 CST 2001
> root at myhost.mydomain.net:/usr/lo
> cal/software/bind-8.2.3/src/bin/named
> Feb 27 13:20:06 myhost named[9152]: named.hosts:3: expected a TTL, got
> "86400"
> Feb 27 13:20:06 myhost named[9152]: named.hosts:3: $TTL bad TTL value
> error near
>  (mydomain.net)
> Feb 27 13:20:06 myhost named[9152]: Zone "mydomain.net" (file
> named.hosts): No d
> efault TTL ($TTL <value>) set, using SOA minimum instead
> Feb 27 13:20:06 myhost named[9152]: named.hosts:6: expected a TTL, got
> "43200"
> Feb 27 13:20:06 myhost named[9152]: named.hosts:6: expected a TTL, got
> "1800"
> Feb 27 13:20:06 myhost named[9152]: named.hosts:7: expected a TTL, got
> "1814400"
> Feb 27 13:20:06 myhost named[9152]: named.hosts:8: expected a TTL, got
> "129600"
> Feb 27 13:20:06 myhost named[9152]: named.hosts: WARNING SOA expire
> value is les
> s than SOA refresh+retry (600 < 600+600)
> Feb 27 13:20:06 myhost named[9152]: named.hosts: WARNING SOA expire
> value is les
> s than refresh + 10 * retry (600 < (600 + 10 * 600))
> Feb 27 13:20:06 myhost named[9152]: named.hosts: WARNING SOA expire
> value is les
> s than 7 days (600)
> Feb 27 13:20:06 myhost named[9152]: named.hosts: WARNING SOA refresh
> value is le
> ss than 2 * retry (600 < 600 * 2)
> Feb 27 13:20:06 myhost named[9152]: master zone "mydomain.net" (IN)
> rejected due
>  to errors (serial 2001022709)
> Feb 27 13:20:06 myhost named[9152]: hint zone "" (IN) loaded (serial 0)
> Feb 27 13:20:06 myhost named[9152]: listening on [1.2.3.4].53 (net0)
> Feb 27 13:20:06 myhost named[9152]: Forwarding source address is
> [0.0.0.0].2345
> Feb 27 13:20:06 myhost named[9153]: Ready to answer queries.
>
> Here are the configuration files that produce the above results.
> -- named.conf
> options {
>         directory "/usr/local/named";
>         statistics-interval 0;
>         listen-on {
>                 1.2.3.4;
>                 127.0.0.1;
>                 };
> };
>
> logging {
>         category lame-servers { null; };
>         category cname { null; };
> };
>
> zone "mydomain.net" in { type master; file "named.hosts"; };
> zone "." in { type hint; file "root.cache"; };
>
> -- named.hosts
> $ORIGIN mydomain.net.
>
> $TTL            86400
> @               IN SOA  myhost.mydomain.net.
> postmaster.myhost.mydomain.net. (
>                         2001022709
>                         43200
>                         1800
>                         1814400
>                         129600 )
>                 NS      myhost.mydomain.net.
>
> mydomain.net.   A       1.2.3.4
> myhost          A       1.2.3.4
> ftp             CNAME   myhost
>
> ; Mail exchange record
> mydomain.net.   MX      0       myhost.mydomain.net.
>
> ; Send our info upstream
> mydomain.net.   NS      theirhost.dnsdomain.net.
>
> Finally, I have a similar configuration running on a SCO OpenServer
> 5.0.4 with no problems.  In fact, I copied the binaries over from that
> server and have the same results.
>
> If you need more information, please let me know.  If you can help me in
> any way, I would appreciate it so that I can upgrade my BIND to the
> latest stable version.
>
> TIA,
> Travis Rayhons
> Dordt College