You don't have an origin nor an A record for ns.example.com. I would replace example.com in the SOA with @ and you are missing the space between the authoritive name server and the email address. Also missing a period at the end of the email address.
I kept my time periods in seconds since that is what dig will give you back when querying the zone. IN for Internet zone is assumed and is not required in the records. Lyle Giese LCR Computer Services, Inc. CT wrote: > old zone file > --------------- > $ORIGIN . > $TTL 3600 > example.com IN SOA ns.example.com. root.example.com ( > 2010071402 ; serial > 10800 ; refresh (3 hours) > 3600 ; retry (1 hour) > 345600 ; expire (4 days) > 86400 ; minimum (1 day) > ) > NS example.com. > > $ORIGIN example.com. > A 192.168.1.1 > MX 10 ns.example.com. > www CNAME example.com. > --------------------- > > proposed new file > --------------------- > $TTL 3600 $origin example.com. > @ IN SOA ns.example.com. root.example.com. ( > 2010071403 ;serial > 3h ;refresh > 1h ;retry > 1w ;expire > 1h ;ncache > ) > IN NS ns.example.com. > IN MX 10 ns.example.com. ns in a 192.168.1.2 > > ;localhost IN A 127.0.0.1 > IN A 192.168.1.1 > www CNAME example.com. > > > My question... > Will my proposed set up work on the "old bind" version.. > and it is syntactically correct ?? > > Thx > Charles > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
