6.3 KiB
page-title, url, date
| page-title | url | date |
|---|---|---|
| [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer | https://mailman.powerdns.com/pipermail/pdns-users/2010-May/018731.html | 2023-04-19 12:18:15 |
David J Craigon david at craigon.co.uk
Wed May 26 13:29:25 UTC 2010
- Previous message: [Pdns-users] Power DNS 2.9.22 compile error while running 'make' command
- Next message: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 <david at craigon.co.uk> 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 <bert.hubert at netherlabs.nl> 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 >> >
- Previous message: [Pdns-users] Power DNS 2.9.22 compile error while running 'make' command
- Next message: [Pdns-users] TCP Connection Thread died because of STL error: Reading data: Connection reset by peer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]