Hi,
I have observer a SERVFAIL error in one of my zone.On checking the logs
I realized there is this error
/journal rollforward failed: journal out of sync with zone/
I tried to learn more about it and I found out the solution is to delete
the journal file and restart bind.I tried that and i
On 12/04/12 11:50, Bryton wrote:
Hi,
I have observer a SERVFAIL error in one of my zone.On checking the logs
I realized there is this error
/journal rollforward failed: journal out of sync with zone/
I tried to learn more about it and I found out the solution is to delete
the journal file and
Not at all.Everything is automated via cron.Zone is generated from one
server cron pushes to another then cron reload bind...
On 04/12/2012 02:03 PM, Phil Mayers wrote:
On 12/04/12 11:50, Bryton wrote:
Hi,
I have observer a SERVFAIL error in one of my zone.On checking the logs
I realized the
On 12/04/2012 14:19, Bryton wrote:
> Not at all.Everything is automated via cron.Zone is generated from one
> server cron pushes to another then cron reload bind...
Hi Bryton,
If you're pushing the zone to the second server (with scp/rsync) and
reloading periodically, there should be no journal.
Hello list,
I'm running bind9 on my local router which is connected to the internet via a
ppp link over my ADSL modem. This link has a static IP assigned, but is not
permanently up. Once a day the connection is dropped for a few seconds and
re-established, which leads to the following problem:
-
You can set interface-interval to a low number to make BIND scan for new
interfaces frequently:
interface-interval
interface-interval minutes;
interface-interval defines the time in MINUTES when scan all interfaces on the
server and will begin to listen on new interfaces (assuming they are no
On 12/04/12 15:32, Mihai Moldovan wrote:
Is there any way to tell bind9 to re-evaluate the network situation and bind to
all new interfaces (if allowed, see listen-on)?
I have tried firing up rndc reload and rndc reconfig via the pppd if-up/if-down
scripts, but neither try was successful.
"rn
* On 12.04.2012 04:49 PM, Phil Mayers wrote:
> "rndc reconfig" has worked when I've tried it in the past; are you sure you're
> running it in the right place? You want to run it in the "ip-up" / "ip-down"
> scripts, because IP might not be up when LCP is.
Absolutely positive. I'm running rndc reco
* On 12.04.2012 04:44 PM, Todd Snyder wrote:
> You can set interface-interval to a low number to make BIND scan for new
> interfaces frequently:
Interesting option! Weird thing is, the documentation as per
/usr/share/doc/bind-9.9.0/html/Bv9ARM.ch06.html says:
The server will scan the network int
On Apr 12, 2012, at 5:19 AM, Bryton wrote:
>
> Not at all.Everything is automated via cron.Zone is generated from one
> server cron pushes to another then cron reload bind...
Figure out why you're getting a journal file. If you need to have a journal
file (i.e. you need whatever mechanism caus
On 12/04/12 16:44, Mihai Moldovan wrote:
Hmm, permission denied while binding to ppp0? Maybe that's because my named is
running as the non-privileged system user "named" and binding to the privileged
port 53? Makes sense... but... hm. I guess in this case there's no other way but
running named a
It probably has to do with BIND dropping privileges.
If you run BIND with "-u" so it changes to an unprivileged user, then BIND may
not be able to bind() to new interfaces created on your system.
I use FreeBSD, and my solution was to do this every time I add a new interface:
RESET=`sysctl -e
You don't necessarily have to get rid of the cron job to keep journal files.
"ixfr-from-differences" is intentionally designed to allow you to arbitrarily
replace the zone file and yet continue to keep your .jnl files.
However, I too have run into rollforward errors with my use of
"ixfr-from-di
* On 12.04.2012 09:11 PM, Mark Pettit wrote:
> If you run BIND with "-u" so it changes to an unprivileged user, then BIND
> may not be able to bind() to new interfaces created on your system.
>
> [...]
>
> What OS are you using, and what's the command-line you use to launch BIND?
I'm using Linux
* On 12.04.2012 10:01 PM, Mihai Moldovan wrote:
> Seems fine... but: I found out my bind was built with --disable-linux-caps and
> --disable-threads... enabling the first option sounds promising (second one is
> just for my own pleasure.)
>
> Rebuilding... I'll report back once I know whether this
Any Reason people could see why this config would not allow remote systems that
can ping this server to do lookups on it?
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
/
On Apr 12, 2012, at 3:38 PM, Dustin Moon wrote:
> Any Reason people could see why this config would not allow remote systems
> that can ping this server to do lookups on it?
Why, yes-- see the following line:
>allow-query { localhost; };
...?
Regards,
--
-Chuck
__
Hi Dustin,
"allow-query { localhost; }" limits queries to localhost. You need to
add your users' network(s) to that ACL.
On 13/04/2012 00:38, Dustin Moon wrote:
> Any Reason people could see why this config would not allow remote
> systems that can ping this server to do lookups on it?
>
>
> /
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
options {
listen-on port 53 { 127.0.0.1
On Apr 12, 2012, at 3:52 PM, Dustin Moon wrote:
> #allow-query { any; };
Commenting it out entirely is *not* the same thing as changing it to a setting
which allows remote clients to make queries.
Regards,
--
-Chuck
___
Please visit https
Mark,
I also do "ixfr-from-differences" and this might be the reason I will
now dig more into this.
Thanks Mark for the clue.
On 04/12/2012 10:05 PM, Mark Pettit wrote:
You don't necessarily have to get rid of the cron job to keep journal files.
"ixfr-from-differences" is intentionally desi
21 matches
Mail list logo
