named won't start -- solved

[Mike Lempriere]

Got it!  Thanks Sergey, the migration doc you pinted out below showed me 
to the real problem.

I had an old directive:
    query-source address * port 53;

Commenting this out now allows named to start.  I'm getting a
    working directory is not writable
error now, but that's something I should be able to figure out myself!

Interestingly enough, I have this same declaration on my secondary 
machine.  That machine just went through the same process, and it did 
not have this problem...

Thanks for all the help guys -- much appreciated!

Sergey N. Voronkov wrote:
> On Wed, Jan 14, 2009 at 08:11:27PM -0800, Mike Lempriere wrote:
>   
>> From /var/log/messages:
>> starting BIND 9.4.3-P1 -t /var/named -u bind
>> could not get query source dispatcher (0.0.0.0#53)
>> loading configuration: address in use
>> exiting (due to fatal error)
>>
>> I had just updated from 5-stable (at 5.5) to 6-stable (at 6.4).  Upon 
>> today's upgrade I got to 7.1.  Everything else seems to be be working 
>> (the machine is basically a webserver), except named.  apache is serving 
>> up pages, but only until my TTL times out...
>>
>> I so no errors in the builds or installs.  I foolwed the instructions in 
>> UPDATING.  I believe I did an accurate merge of my named.conf file.
>>
>> This is a production machine, with paying customers -- please help!  
>> Thank you!
>>
>>     
>
> http://www.fiveanddime.net/bind-9/bind-9.3.1/doc/misc/migration..html
>
> "6. No Information Leakage between Zones"
>
> "Sites that were relying on this BIND 8 behaviour need to add any
> omitted glue NS records, and any necessary glue A records, to the
> parent zone."
>
> Did You insert NS and A records into parent zone files?
>
> Serg N. Voronkov,
> Sibitex Ltd.
>
>
>
>   

-- 
Mike Lempriere- Home: mike at vintners.net  Phone: 206-780-2146
Cellphone: 206-200-5902;  text pager: mikelemp at tmail.com