On Thu, Jan 18, 2007 at 11:47:44AM -0500, Gerald Britton wrote:
Hi -- I'm just getting started with pdns on ubuntu edgy. I installed
it using synaptic, which also starts the daemon. I tried a bunch of
stuff, e.g. using firefox to visit several websites, then stopped
firefox, lauched it again
Hmm -- more trouble here:
$ pdns_control counts
Fatal error: Unable to connect to remote
'/var/run/pdns.controlsocket': Permission denied
[EMAIL PROTECTED]:~/gramps2$ sudo pdns_control counts
After restartinf pdns, the syslog shows this:
Jan 18 12:06:30 localhost pdns[15472]: Listening on
Hi,
I have a problem with pdns. When I add a zone in my primary server I
receive this message from pdns:
Created new slave zone 'zzz.com' from supermaster xxx.xxx.xxx.xxx,
queued axfr
AXFR started for 'zzz.com', transaction started
Communicator thread died because of error: Database failed to
On Thu, Jan 18, 2007 at 12:11:57PM -0500, Gerald Britton wrote:
Hmm -- more trouble here:
Try as root. Also, you need rec_control for the pdns_recursor. Do you
actually need authoritative domains? You can run the recursor standalone
without an authoritative frontend.
Just starting pdns_recursor
On Thu, Jan 18, 2007 at 12:30:53PM -0500, Gerald Britton wrote:
Oh, I get it, only pdsn_recursor is running! So I used rec_control to
dump the cache, which only has the basic entries. Then I did a bunch
of host commands (cnn.com, powerdns.com, etc) to try to get some more
in there, but when
Ah -- so I should modify resolv.conf to point to localhost, right? If
so, that leads to an interesting problem, since resolv.conf is updated
by dhcp. Also, I've seen the nameservers in resolv.conf change from
time to time. Any idea how to get around this?
On 1/18/07, bert hubert [EMAIL
I see, but won't that force the namserver to the localhost? How will
the recursor know where to forward requests not resolved by the cache?
On 1/18/07, Christian Hofstädtler [EMAIL PROTECTED] wrote:
--On 18/1/2007 12:38 -0500 Gerald Britton [EMAIL PROTECTED] wrote:
Ah -- so I should modify
It is my understanding, that pdns-recursor will never query forwarders,
except for explicitly configured zones (see forward-zones setting).
Instead, it will just query the root nameservers directly; the root
nameserver IP addresses are hard-coded inside the recursor, but you can
override them
Hi guys,
We've run PowerDNS on our authoritative name servers for quite some
time; however, I noticed after upgrading to 2.9.20 that after the name
server is running for X days, TCP queries just time out and restarting
the PowerDNS service fixes the problem.
Has anyone experienced anything
On Thu, Jan 18, 2007 at 03:26:51PM -0600, Jeff Fisher wrote:
We've run PowerDNS on our authoritative name servers for quite some
time; however, I noticed after upgrading to 2.9.20 that after the name
server is running for X days, TCP queries just time out and restarting
the PowerDNS service
10 matches
Mail list logo