What's wrong with this zone file?
Michael Voight
mvoight at cisco.com
Wed Jun 16 18:04:33 UTC 1999
Don't use 0 in front of the number. It is .2, not .02.
Michael
Steve Snyder wrote:
>
> Following the directions in the 3rd edition of "DNS and BIND" I
> hand-created a zone database from the data in my /etc/hosts file. When I
> started named, it consistently complained about the same 2 records.
>
> I inspected the file over and over and in several different editors, trying
> to determine how these 2 records were different from all the others. They
> looked good to me. Finally, I downloaded the utility h2n (used in the
> book) and had it automatically create the files. Named still issues the
> same complaints! The records complained about are the same, though now on
> different lines in the file.
>
> This is the complaint I get:
>
> corona named[1011]: db.snydernet:25: IP Address error (192.168.0.08)
> corona named[1011]: db.snydernet:27: IP Address error (192.168.0.09)
> corona named[1011]: master zone "snydernet.lan" (IN) rejected due to errors (serial 1999061600)
>
> And this is db.snydernet, the zone file containing the "bad" records:
>
> @ IN SOA corona.snydernet.lan. root.corona.snydernet.lan. ( 1999061600 10800 3600 604800 86400 )
> IN NS corona.snydernet.lan.
>
> localhost IN A 127.0.0.1
> ljet4m IN A 192.168.0.16
> ljet4m IN MX 10 ljet4m.snydernet.lan.
> venus IN A 192.168.0.03
> venus IN MX 10 venus.snydernet.lan.
> dj1120 IN A 192.168.0.17
> dj1120 IN MX 10 dj1120.snydernet.lan.
> corona IN A 192.168.0.12
> corona IN MX 10 corona.snydernet.lan.
> jupiter IN A 192.168.0.06
> jupiter IN MX 10 jupiter.snydernet.lan.
> mars IN A 192.168.0.05
> mars IN MX 10 mars.snydernet.lan.
> pluto IN A 192.168.0.10
> pluto IN MX 10 pluto.snydernet.lan.
> earth IN A 192.168.0.04
> earth IN MX 10 earth.snydernet.lan.
> mercury IN A 192.168.0.02
> mercury IN MX 10 mercury.snydernet.lan.
> saturn IN A 192.168.0.07
> saturn IN MX 10 saturn.snydernet.lan.
> uranus IN A 192.168.0.08
> uranus IN MX 10 uranus.snydernet.lan.
> neptune IN A 192.168.0.09
> neptune IN MX 10 neptune.snydernet.lan.
>
> Named always objects to the "uranus" and "neptune" IN records. If I
> comment-out these 2 records, named will start up without error.
>
> Can anyone tell me why these 2 specific records are considered
> unacceptable? Thank you.
>
> ***** Steve Snyder *****
More information about the bind-users
mailing list