Thanks Eric, (and everybody)
Using the text notation of the address followed by a dot corrected the strange
sysquery.
I tried removing the dot but in a NS record it will append the domain to end
(even though it was given a dot.quad). If I use the text notation with a dot
everything goes well.
thanks
Eric Cifreo wrote:
> ----- Original Message -----
> From: Robert Canary <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, December 05, 1999 9:30 PM
> Subject: Re: broken zone(s) Oops! Spoke to soon
>
> > Still getting this damn things :-)
> > Any ideas why?
> >
> > Dec 5 22:20:04 mchn3 named[1612]: Sent NOTIFY for "6.32.208.in-addr.arpa
> IN SOA"
> > (6.32.208.in-addr.arpa); 1 NS, 1 A
> > Dec 5 22:20:09 mchn3 named[1612]: sysquery: sendto([0.0.104.81].53):
> Invalid argument
> >
> > Dec 5 22:20:09 mchn3 named[1612]: sysquery: sendto([0.0.136.81].53):
> Invalid argument
>
> It looked like in your zone files, you had appended a dot after your NS
> records dotted quads. You only need to do this for text records. For
> example,
> No trailing dot here:
> @ IN NS 208.32.6.20.
>
> But you need one here, or named will append your $DOMAINNAME.
> IN NS mchn3.ohiocounty.net.
>
> Hope that clears it up....
>
> Eric Cifreo
> Austin, TX
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
robert canary
system services
OhioCounty.Net
[EMAIL PROTECTED]
(270)298-9331 Office
(270)298-7449 Fax
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
