Can't find server name for address 127.0.0.1: Server failed

[Michael J. Pape]

Thanks for the reply,

The TTL directive is necessary for the zones to load as per reasons stated
in the doc/misc/migration document. I guess what threw me here was that
while the "no TTL" messages were logged, there were no messages logged that
explicitly stated that the zones were not being loaded. Furthermore, the
message log ended the 9.1 start up with a "running" message. I incorrectly
assumed at this point that a default value was being used  -- as was the
case for BIND 8... Perhaps running named at a non-default debugging level
would have helped...

Thanks again,
mike


-----Original Message-----
From: marka at nominum.com [mailto:marka at nominum.com]On Behalf Of
Mark.Andrews at nominum.com
Sent: Wednesday, January 31, 2001 6:05 PM
To: Michael J. Pape
Cc: BIND
Subject: Re: Can't find server name for address 127.0.0.1: Server failed




>
>
> I'm upgrading from 8.2.2p5 to 9.1. Everything seems to start fine -- aside
> from the "no TTL specified" messages that I'll get to shortly.
>
> The problem is that after verifying that named version 9.1 is running, I
get
> the following when using nslookup:
>
> *** Can't find server name for address 127.0.0.1: Server failed
> *** Default servers are not available
>
> named-checkconf returns:
> the default for the 'auth-nxdomain' option is now 'no'
>
> and named-checkzone returns:
> dns_master_load: db.106.149:4: no TTL specified
> dns_zone_load: zone db.106.149/IN: loading master file db.106.149: no ttl
>
> Would fixing the TTL errors help?
> Any clues???

	How about the FAQ, README or doc/migration which is mentioned in
	README.

	Mark
>
> Thanks,
> mike
>
>
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com