Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
Yes. As Seth pointed out, the generic-* backend does not support Autoserial. Try the OpenDBX backend which has Autoserial support since 2.9.22. Regards, Ken On Wed, May 26, 2010 at 09:22:47PM -0700, Seth Mattinen wrote: > On 5/26/10 6:29 AM, David J Craigon wrote: > > > > Any idea how to get automatic serial numbers working? > > > > Autoserial is not supported in the generic backends: > > http://doc.powerdns.com/generic-mypgsql-backends.html > > Table A-5. Generic PgSQL and MySQL backend capabilities > NativeYes - but PostgreSQL does not replicate > MasterYes > Slave Yes > SuperslaveYes > AutoserialNO > > ~Seth > ___ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users > ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
On 5/26/10 6:29 AM, David J Craigon wrote: > > Any idea how to get automatic serial numbers working? > Autoserial is not supported in the generic backends: http://doc.powerdns.com/generic-mypgsql-backends.html Table A-5. Generic PgSQL and MySQL backend capabilities Native Yes - but PostgreSQL does not replicate Master Yes Slave Yes Superslave Yes Autoserial NO ~Seth ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
I've got to the bottom of it, sort of.
Firstly, only dig seems to cause this problem If I try it with
nslookup on Windows, it seemed to work.
It works if I put in a manual serial number in the SOA records.
Otherwise PowerDNS was putting out 0 a serial number in the SOA, which
dig didn't like.
Any idea how to get automatic serial numbers working?
According to the manual:
"If left at 0, the default, PDNS will perform an internal list of the
domain to determine highest change_date field of all records within
the zone, and use that as the zone serial number. "
So what goes in the change_date field? I tried putting 20100526 as a
numerical representation of now, but it was still putting out 0 as a
serial number.
David
On 26 May 2010 12:21, David J Craigon wrote:
> DB schema is exactly as here:
>
> http://doc.powerdns.com/generic-mypgsql-backends.html
>
> with the only difference that I have put these tables in a schema
> "dns" in the database, since I want to use the database for other
> things too.
>
> These are my database queries- they are exactly the same as the
> defaults, except for adding dns. to the beginning of every table name.
>
> # database queries
>
> gpgsql-basic-query=select content,ttl,prio,type,domain_id,name from
> dns.records where type='%s' and name='%s'
>
> gpgsql-id-query=select content,ttl,prio,type,domain_id,name from
> dns.records where type='%s' and name='%s' and domain_id=%d
>
> gpgsql-any-query=select content,ttl,prio,type,domain_id,name from
> dns.records where name='%s'
>
> gpgsql-any-id-query=select content,ttl,prio,type,domain_id,name from
> dns.records where name='%s' and domain_id=%d
>
> gpgsql-list-query=select content,ttl,prio,type,domain_id,name from
> dns.records where domain_id=%d
>
>
>
> gpgsql-master-zone-query=select master from dns.domains where
> name='%s' and type='SLAVE'
>
> gpgsql-info-zone-query=select
> id,name,master,last_check,notified_serial,type from dns.domains where
> name='%s'
>
> gpgsql-info-all-slaves-query=select id,name,master,last_check,type
> from dns.domains where type='SLAVE'
>
> gpgsql-supermaster-query=select account from dns.supermasters where
> ip='%s' and nameserver='%s');
>
> gpgsql-insert-slave-query=insert into dns.domains
> (type,name,master,account) values('SLAVE','%s','%s','%s')
>
> gpgsql-insert-record-query=insert into dns.records
> (content,ttl,prio,type,domain_id,name) values
> ('%s',%d,%d,'%s',%d,'%s')
>
> gpgsql-update-serial-query=update dns.domains set notified_serial=%d where
> id=%d
>
> gpgsql-update-lastcheck-query=update dns.domains set
> notified_serial=%d where id=%d
>
> gpgsql-info-all-master-query=select
> id,name,master,last_check,notified_serial,type from dns.domains where
> type='MASTER'
>
> gpgsql-delete-zone-query=delete from dns.records where domain_id=%d
>
>
>
> gpgsql-wildcard-query=select content,ttl,prio,type,domain_id,name from
> dns.records where type='%s' and name like '%s'
>
> gpgsql-wildcard-id-query=select content,ttl,prio,type,domain_id,name
> from dns.records where type='%s' and name like '%s' and domain_id=%d
>
> gpgsql-wildcard-any-query=select content,ttl,prio,type,domain_id,name
> from dns.records where name like '%s'
>
> gpgsql-wildcard-any-id-query=select
> content,ttl,prio,type,domain_id,name from dns.records where name='%s'
> and domain_id=%d
>
>
> David
>
> On 26 May 2010 12:00, bert hubert wrote:
>> On Wed, May 26, 2010 at 11:59:31AM +0100, David J Craigon wrote:
>>> Adding a TTL doesn't help. Without one, ordinary queries are responded
>>> to with the default TTL.
>>
>> Ok - can you show all your queries from the configuration? And your db
>> schema?
>>
>> Bert
>>
>
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
DB schema is exactly as here:
http://doc.powerdns.com/generic-mypgsql-backends.html
with the only difference that I have put these tables in a schema
"dns" in the database, since I want to use the database for other
things too.
These are my database queries- they are exactly the same as the
defaults, except for adding dns. to the beginning of every table name.
# database queries
gpgsql-basic-query=select content,ttl,prio,type,domain_id,name from
dns.records where type='%s' and name='%s'
gpgsql-id-query=select content,ttl,prio,type,domain_id,name from
dns.records where type='%s' and name='%s' and domain_id=%d
gpgsql-any-query=select content,ttl,prio,type,domain_id,name from
dns.records where name='%s'
gpgsql-any-id-query=select content,ttl,prio,type,domain_id,name from
dns.records where name='%s' and domain_id=%d
gpgsql-list-query=select content,ttl,prio,type,domain_id,name from
dns.records where domain_id=%d
gpgsql-master-zone-query=select master from dns.domains where
name='%s' and type='SLAVE'
gpgsql-info-zone-query=select
id,name,master,last_check,notified_serial,type from dns.domains where
name='%s'
gpgsql-info-all-slaves-query=select id,name,master,last_check,type
from dns.domains where type='SLAVE'
gpgsql-supermaster-query=select account from dns.supermasters where
ip='%s' and nameserver='%s');
gpgsql-insert-slave-query=insert into dns.domains
(type,name,master,account) values('SLAVE','%s','%s','%s')
gpgsql-insert-record-query=insert into dns.records
(content,ttl,prio,type,domain_id,name) values
('%s',%d,%d,'%s',%d,'%s')
gpgsql-update-serial-query=update dns.domains set notified_serial=%d where id=%d
gpgsql-update-lastcheck-query=update dns.domains set
notified_serial=%d where id=%d
gpgsql-info-all-master-query=select
id,name,master,last_check,notified_serial,type from dns.domains where
type='MASTER'
gpgsql-delete-zone-query=delete from dns.records where domain_id=%d
gpgsql-wildcard-query=select content,ttl,prio,type,domain_id,name from
dns.records where type='%s' and name like '%s'
gpgsql-wildcard-id-query=select content,ttl,prio,type,domain_id,name
from dns.records where type='%s' and name like '%s' and domain_id=%d
gpgsql-wildcard-any-query=select content,ttl,prio,type,domain_id,name
from dns.records where name like '%s'
gpgsql-wildcard-any-id-query=select
content,ttl,prio,type,domain_id,name from dns.records where name='%s'
and domain_id=%d
David
On 26 May 2010 12:00, bert hubert wrote:
> On Wed, May 26, 2010 at 11:59:31AM +0100, David J Craigon wrote:
>> Adding a TTL doesn't help. Without one, ordinary queries are responded
>> to with the default TTL.
>
> Ok - can you show all your queries from the configuration? And your db schema?
>
> Bert
>
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
On Wed, May 26, 2010 at 11:59:31AM +0100, David J Craigon wrote: > Adding a TTL doesn't help. Without one, ordinary queries are responded > to with the default TTL. Ok - can you show all your queries from the configuration? And your db schema? Bert ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
Adding a TTL doesn't help. Without one, ordinary queries are responded to with the default TTL. David On 26 May 2010 11:07, bert hubert wrote: > On Wed, May 26, 2010 at 10:43:04AM +0100, David J Craigon wrote: >> isp=# select * from dns.records; >> id | domain_id | name | type | >> content | ttl | prio | change_date >> +---+---+--+---+-+--+- >> 3 | 2 | 1.48.69.109.in-addr.arpa | PTR | >> gw-5.core1.littleowlhosting.com | | > > Very quick response, I did not study this too well, but no TTL? > Tends to matter. > > Bert > ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
On Wed, May 26, 2010 at 10:43:04AM +0100, David J Craigon wrote: > isp=# select * from dns.records; > id | domain_id | name | type | > content | ttl | prio | change_date > +---+---+--+---+-+--+- > 3 | 2 | 1.48.69.109.in-addr.arpa | PTR | > gw-5.core1.littleowlhosting.com | | Very quick response, I did not study this too well, but no TTL? Tends to matter. Bert ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
Hello, I'm trying to use zone transfers but they are not working. With the logging turned up high, I am getting "TCP Connection Thread died because of STL error: Reading data: Connection reset by peer" in /var/log/messages. I only get one record sent. This is even when doing dig -t AXFR @localhost 49.69.109.in-addr.arpa I'm using the postgresql backend. Here are what my tables look like: isp=# select * from dns.domains; id | name | master | last_check | type | notified_serial | account +++++-+- 3 | 49.69.109.in-addr.arpa | | | MASTER | | 4 | 50.69.109.in-addr.arpa | | | MASTER | | 5 | 51.69.109.in-addr.arpa | | | MASTER | | 2 | 48.69.109.in-addr.arpa | | | MASTER | 0 | (4 rows) isp=# select * from dns.records; id | domain_id | name | type | content | ttl | prio | change_date +---+---+--+---+-+--+- 3 | 2 | 1.48.69.109.in-addr.arpa | PTR | gw-5.core1.littleowlhosting.com | | | 4 | 2 | 2.48.69.109.in-addr.arpa | PTR | gw-5.core2.littleowlhosting.com | | | 5 | 2 | 3.48.69.109.in-addr.arpa | PTR | linux-infrastructure.littleowlhosting.com | | | 6 | 2 | 25.48.69.109.in-addr.arpa | PTR | gw-4.core1.littleowlhosting.com | | | 7 | 2 | 26.48.69.109.in-addr.arpa | PTR | gw-4.core2.littleowlhosting.com | | | 8 | 2 | 33.48.69.109.in-addr.arpa | PTR | gw-9.core1.littleowlhosting.com | | | 9 | 2 | 34.48.69.109.in-addr.arpa | PTR | gw-9.core2.littleowlhosting.com | | | 10 | 2 | 49.48.69.109.in-addr.arpa | PTR | gw-12.core1.littleowlhosting.com | | | 11 | 2 | 50.48.69.109.in-addr.arpa | PTR | gw-12.core2.littleowlhosting.com | | | 12 | 2 | 65.48.69.109.in-addr.arpa | PTR | gw-13.core1.littleowlhosting.com | | | 13 | 2 | 66.48.69.109.in-addr.arpa | PTR | gw-13.core2.littleowlhosting.com | | | 14 | 2 | 48.69.109.in-addr.arpa | SOA | ns1.dns.littleowlhosting.com supp...@littleowlhosting.com | | | 15 | 2 | 22.48.69.109.in-addr.arpa | PTR | dns1.r-dns.littleowlhosting.com | | | 16 | 2 | 18.48.69.109.in-addr.arpa | PTR | dns2.r-dns.littleowlhosting.com | | | 17 | 2 | 48.69.109.in-addr.arpa | NS | ns1.dns.littleowlhosting.com | | | 18 | 2 | 48.69.109.in-addr.arpa | NS | ns01.backupdns.com The only configuration change I have made is to put all of the tables in the "dns" schema, so I have modified the queries in /etc/pdns/pdns.conf. Any ideas why it doesn't work? David ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
