Ah, gotcha -- I'm not using any secondary domains so this is not an
issue for me. I do have an internal network, but it's mostly blocked by
ipfw/nat and doesn't have a subdomain name.
Thanks for explaining!
Sergey N. Voronkov wrote:
On Thu, Jan 15, 2009 at 05:30:23AM -0800, Mike Lempriere
Thanks for getting back to me...
I guess I was a little panicy when I entered my note, I didn't explain
much about what I'd already done. There was no named running, 'ps ax |
grep named' showed only my grep and syslog.
'rndc' simply returns a connection refused error, I assume this is a
I'm not real clear on what item 6 means. However all of my specified
zones have at least one NS and one A record. Does this mean I'm Ok?
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
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
On Thu, Jan 15, 2009 at 05:30:23AM -0800, Mike Lempriere wrote:
I'm not real clear on what item 6 means. However all of my specified
zones have at least one NS and one A record. Does this mean I'm Ok?
Sites that were relying on this BIND 8 behaviour need to add any
omitted glue NS records,
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
Mike Lempriere wrote:
loading configuration: address in use
This error generally means that the old named is still running. Try
'rndc stop', and then do 'ps -ax | grep named'. If you still see
something running do '/etc/rc.d/named stop' check ps again, then when
you're sure no other named is
