[Pdns-users] CNAME pointing to URL forwarding record

2011-03-30 Thread Anthony Eden
When I point a CNAME record to a URL forwarding record PowerDNS returns a
SERVFAIL for the CNAME query when I go through a resolver. If I dig directly
against the authoritative server it works just fine. Any suggestions on how
I can fix this, other than just replacing the CNAME with another URL
forwarding record?

Thanks!

Sincerely,
Anthony Eden

-- 
http://anthonyeden.com | twitter: @aeden | skype: anthonyeden
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


[Pdns-users] current svn crushes...

2011-03-30 Thread Vasiliy G Tolstov
I'm build current svn trunk, something work's fine, but sometimes i get
this error:

Mar 30 14:33:34 monitoring pdns[28785]: Got a signal 11, attempting to
print trace: 
Mar 30 14:33:34 monitoring pdns[28785]: /usr/sbin/pdns_server-instance
[0x813a614]
Mar 30 14:33:34 monitoring pdns[28785]: [0x604420]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16 [0x2c1221]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16(my_net_read+0x1a0)
[0x2c15a0]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16(cli_safe_read+0x48)
[0x2ba658]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16 [0x2bb555]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16(mysql_real_query+0x44)
[0x2b9ce4]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/lib/mysql/libmysqlclient.so.16(mysql_query+0x35)
[0x28fcf5]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/sbin/pdns_server-instance(_ZN6SMySQL7doQueryERKSs
+0x13e) [0x80b538e]
Mar 30 14:33:34 monitoring
pdns[28785]: /usr/sbin/pdns_server-instance(_ZN11GSQLBackend8setFreshEj
+0x73) [0x81acd53]
Mar 30 14:33:34 monitoring
pdns[28785]: 
/usr/sbin/pdns_server-instance(_ZN17CommunicatorClass12slaveRefreshEP13PacketHandler+0x1a8b)
 [0x8169c2b]
Mar 30 14:33:34 monitoring
pdns[28785]: 
/usr/sbin/pdns_server-instance(_ZN17CommunicatorClass8mainloopEv+0x11c) 
[0x8175f5c]
Mar 30 14:33:34 monitoring
pdns[28785]: 
/usr/sbin/pdns_server-instance(_ZN17CommunicatorClass12launchhelperEPv+0x11) 
[0x8176e41]
Mar 30 14:33:34 monitoring pdns[28785]: /lib/libpthread.so.0 [0xcdd832]
Mar 30 14:33:34 monitoring pdns[28785]: /lib/libc.so.6(clone+0x5e)
[0x570f6e]
Mar 30 14:33:35 monitoring pdns[23474]: Our pdns instance (28785) exited
after signal 6


Full log:

Mar 30 14:33:30 monitoring pdns[28785]: Guardian is launching an
instance
Mar 30 14:33:30 monitoring pdns[28785]: Reading random entropy from
'/dev/urandom'
Mar 30 14:33:30 monitoring pdns[28785]: This is a guarded instance of
pdns
Mar 30 14:33:30 monitoring pdns[28785]: UDP server bound to
89.249.18.120:53
Mar 30 14:33:30 monitoring pdns[28785]: TCP server bound to
89.249.18.120:53
Mar 30 14:33:30 monitoring pdns[28785]: PowerDNS 3.0-rc1 (C) 2001-2011
PowerDNS.COM BV (Mar 30 2011, 14:01:21, gcc 4.1.2 20080704 (Red Hat
4.1.2-48)) starting up
Mar 30 14:33:30 monitoring pdns[28785]: PowerDNS comes with ABSOLUTELY
NO WARRANTY. This is free software, and you are welcome to redistribute
it according to the terms of the GPL version 2.
Mar 30 14:33:30 monitoring pdns[28785]: Creating backend connection for
TCP
Mar 30 14:33:30 monitoring pdns[28785]: Master/slave communicator
launching
Mar 30 14:33:30 monitoring pdns[28785]: gmysql Connection successful
Mar 30 14:33:30 monitoring last message repeated 2 times
Mar 30 14:33:30 monitoring pdns[28785]: About to create 3 backend
threads for UDP
Mar 30 14:33:30 monitoring pdns[28785]: gmysql Connection successful
Mar 30 14:33:30 monitoring last message repeated 6 times
Mar 30 14:33:30 monitoring pdns[28785]: Done launching threads, ready to
distribute questions
Mar 30 14:33:31 monitoring pdns[28785]: gmysql Connection successful
Mar 30 14:33:31 monitoring pdns[28785]: No new unfresh slave domains, 0
queued for AXFR already
Mar 30 14:33:34 monitoring pdns[28785]: gmysql Connection successful
Mar 30 14:33:34 monitoring pdns[28785]: 17 slave domains need checking,
0 queued for AXFR
Mar 30 14:33:34 monitoring pdns[28785]: Received serial number updates
for 17 zones, had 0 timeouts
Mar 30 14:33:34 monitoring pdns[28785]: Domain 236.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 237.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 238.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 239.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 240.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 241.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 244.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 245.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 40.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 41.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 42.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 43.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:33:34 monitoring pdns[28785]: Domain 44.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 

Re: [Pdns-users] current svn crushes...

2011-03-30 Thread bert hubert
On Wed, Mar 30, 2011 at 02:36:14PM +0400, Vasiliy G Tolstov wrote:
 I'm build current svn trunk, something work's fine, but sometimes i get
 this error:

Hi Vasiliy,

Can you verify that the crash always starts:

 pdns[28785]: /usr/sbin/pdns_server-instance(_ZN11GSQLBackend8setFreshEj
 +0x73) [0x81acd53]
 Mar 30 14:33:34 monitoring
 pdns[28785]: 
 /usr/sbin/pdns_server-instance(_ZN17CommunicatorClass12slaveRefreshEP13PacketHandler+0x1a8b)
  [0x8169c2b]
 Mar 30 14:33:34 monitoring

Here?

If it doesn't always start there, can you paste some other traces?

Thanks!
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] current svn crushes...

2011-03-30 Thread Vasiliy G Tolstov
On Wed, 2011-03-30 at 12:47 +0200, bert hubert wrote:
 On Wed, Mar 30, 2011 at 02:36:14PM +0400, Vasiliy G Tolstov wrote:
  I'm build current svn trunk, something work's fine, but sometimes i get
  this error:
 
 Hi Vasiliy,
 
 Can you verify that the crash always starts:
 
  pdns[28785]: /usr/sbin/pdns_server-instance(_ZN11GSQLBackend8setFreshEj
  +0x73) [0x81acd53]
  Mar 30 14:33:34 monitoring
  pdns[28785]: 
  /usr/sbin/pdns_server-instance(_ZN17CommunicatorClass12slaveRefreshEP13PacketHandler+0x1a8b)
   [0x8169c2b]
  Mar 30 14:33:34 monitoring
 
 Here?
 
 If it doesn't always start there, can you paste some other traces?
 
 Thanks!

Another crush:

Mar 30 14:51:57 monitoring pdns[31390]: Guardian is launching an
instance
Mar 30 14:51:57 monitoring pdns[31390]: Reading random entropy from
'/dev/urandom'
Mar 30 14:51:57 monitoring pdns[31390]: This is a guarded instance of
pdns
Mar 30 14:51:57 monitoring pdns[31390]: UDP server bound to
89.249.18.120:53
Mar 30 14:51:57 monitoring pdns[31390]: TCP server bound to
89.249.18.120:53
Mar 30 14:51:57 monitoring pdns[31390]: PowerDNS 3.0-rc1 (C) 2001-2011
PowerDNS.COM BV (Mar 30 2011, 14:01:21, gcc 4.1.2 20080704 (Red Hat
4.1.2-48)) starting up
Mar 30 14:51:57 monitoring pdns[31390]: PowerDNS comes with ABSOLUTELY
NO WARRANTY. This is free software, and you are welcome to redistribute
it according to the terms of the GPL version 2.
Mar 30 14:51:57 monitoring pdns[31390]: Creating backend connection for
TCP
Mar 30 14:51:57 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:51:57 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:51:57 monitoring pdns[31390]: Master/slave communicator
launching
Mar 30 14:51:57 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:51:57 monitoring pdns[31390]: About to create 3 backend
threads for UDP
Mar 30 14:51:57 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:51:57 monitoring pdns[31390]: Done launching threads, ready to
distribute questions
Mar 30 14:51:58 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:51:58 monitoring pdns[31390]: No new unfresh slave domains, 0
queued for AXFR already
Mar 30 14:51:58 monitoring pdns[31390]: No master domains need
notifications
Mar 30 14:52:03 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:52:03 monitoring pdns[31390]: 7 slave domains need checking, 0
queued for AXFR
Mar 30 14:52:03 monitoring pdns[31390]: Received serial number updates
for 7 zones, had 0 timeouts
Mar 30 14:52:03 monitoring pdns[31390]: Domain 236.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 237.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 238.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 239.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 241.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 245.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain clodo.ru is fresh (not
presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:52:03 monitoring pdns[31390]: 10 slave domains need checking,
0 queued for AXFR
Mar 30 14:52:03 monitoring pdns[31390]: Received serial number updates
for 10 zones, had 0 timeouts
Mar 30 14:52:03 monitoring pdns[31390]: Domain 240.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 244.127.188.in-addr.arpa
is fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 40.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 41.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 42.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 43.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 44.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 45.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 46.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:03 monitoring pdns[31390]: Domain 47.76.62.in-addr.arpa is
fresh (not presigned, no RRSIG check)
Mar 30 14:52:04 monitoring pdns[31390]: gmysql Connection successful
Mar 30 14:52:10 monitoring pdns[31390]: 17 slave domains need checking,
0 queued for AXFR
Mar 30 14:52:10 monitoring pdns[31390]: Received serial number updates
for 17 zones, had 0 timeouts
Mar 30 14:52:10 monitoring pdns[31390]: Domain 236.127.188.in-addr.arpa
is fresh (not presigned, 

Re: [Pdns-users] CNAME pointing to URL forwarding record

2011-03-30 Thread Stefan Schmidt
Hi Anthony,

On Wed, Mar 30, 2011 at 10:22 AM, Anthony Eden anthonye...@gmail.comwrote:

 When I point a CNAME record to a URL forwarding record PowerDNS returns a
 SERVFAIL for the CNAME query when I go through a resolver. If I dig directly
 against the authoritative server it works just fine. Any suggestions on how
 I can fix this, other than just replacing the CNAME with another URL
 forwarding record?


Please tell us what you dig for and which server - presumably yours - you
are asking.
As there is no such thing as a URL forwarding record in DNS in general, is
it safe to assume that you mean a URL fancy record type such as in
http://doc.powerdns.com/fancy-records.html ?


 Stefan
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


[Pdns-users] Forward IPv6 Requests?

2011-03-30 Thread Pascal R.
HI,

my PDNS currently do IPv4 recursion with the following config:

recursor=8.8.8.8


How can i add an IPV6 Recorder to the pdns.conf ?

thx!
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Forward IPv6 Requests?

2011-03-30 Thread Maik Zumstrull
On Wed, Mar 30, 2011 at 18:41, Pascal R. repa...@gmail.com wrote:
 HI,
 my PDNS currently do IPv4 recursion with the following config:
 recursor=8.8.8.8

 How can i add an IPV6 Recorder to the pdns.conf ?

I believe that is currently not supported, and the functionality may
not be added. In fact, the recursor= option might be removed entirely,
because mixed auth/rec is a bad idea.

Fortunately, it should be unnecessary. You can ask for IPv6 records
while talking to the recursor over IPv4 and vice-versa. You can also
lookup records only available over IPv6 as long as the recursor has a
v6 interface; you can still send your question to the recursor over v4
in this case.

Google Public DNS doesn't support IPv6-only authoritative nameservers
at this time, but they will add that functionality when it seems
necessary.
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Forward IPv6 Requests?

2011-03-30 Thread Nick Milas

On 30/3/2011 7:41 μμ, Pascal R. wrote:


HI,

my PDNS currently do IPv4 recursion with the following config:

recursor=8.8.8.8


How can i add an IPV6 Recorder to the pdns.conf ?



This is what I use in my pdns.conf:

local-address=127.0.0.1 10.10.10.10
do-ipv6-additional-processing=yes
local-ipv6=::1 2001:::::
local-port=53
allow-axfr-ips=10.10.10.10, 10.10.11.10
recursor=127.0.0.1:5300

And in recursor.conf (hosted on the same box):

local-address=127.0.0.1,10.10.10.10,[::1],[2001:::::]
allow-from=0.0.0.0/0,::/0
query-local-address6=2001:::::
local-port=5300
-additional-processing=on

10.10.10.10 is the IPv4 address of the box (it is public, and I have 
replaced it).

2001::::: is always my IPv6 address of the box (public too).

I can't tell whether this is the best configuration (I welcome all 
comments), but it works.


As Maik has said, in fact we communicate with the recursor over local 
IPv4 (at a different port). It is true that it's better to have a 
different box for auth and recursion, but we have a low volume of DNS 
queries and it's not a problem at this time.


Hope that helps.

Nick
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users