Robert Canary on Sun 5/12 17:02 -0600:
> What is wrong with the zone file?
>
> ; Zone file for wxmzfm.com
> ;
> @ IN SOA mchn3.ohiocounty.net. rwcanary.ohiocounty.net. (
> 2147483647 ; serial
> 8 ; refresh
> 2 ; retry
> 1 ; expire
> 1 ; default_ttl
> )
> ;
> @ IN NS 208.32.6.30.
> @ IN NS 208.32.6.20.
> @ IN MX 10 mail
You do not need the `@'s; they are implied.
Your NS records should be hostnames, and FQDNs if they are not in `@'
(or, the zone this file represents with "zone" statement). They should
include glue A records if you do not already have them in the database.
The A records' fields that contain IP addresses do not need trailing
dots.
Your MX record should not point to a CNAME. It also should point to a
FQDN if not in `@' and have glue if it's not already in the zone.
> ;
> localhost IN A 127.0.0.1
This belongs in a separate database.
> named.ohiocounty.net): No default TTL set using SOA minimum instead
You can get rid of these by setting a $TTL for the zone, at top. They
are not harmful errors, however.
> Dec 5 17:16:18 mchn3 named[1098]: listening on [127.0.0.1].53 (lo)
> Dec 5 17:16:18 mchn3 named[1098]: listening on [208.32.6.3].53 (eth0)
> [...]
> Dec 5 17:16:43 mchn3 named[1099]: sysquery: sendto([0.0.136.81].53):
> Invalid argument
Why it's trying to send there, I have no idea, but it's obviously wrong.
--
Scott
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
