[Pdns-users] Pdns Recursor prefetch
Hello. I am checking at the moment different DNS Resolver. We are using for a long time already PDNS Recursor. I have checked already different Recursor like Knot Resolver and Unbound . These are using prefetch. Do we have benefits with prefetching, or is this not needed? Best regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] No DNS entry for mail-eu2.powerdns.net
Hello, when I check my Email Server log I found the following entry. Received: from mail-eu2.powerdns.net (unknown [85.17.219.218]) eka# host mail-eu2.powerdns.net Host mail-eu2.powerdns.net not found: 3(NXDOMAIN) eka# host 85.17.219.218 218.219.17.85.in-addr.arpa domain name pointer hosted.by.trilab.com. I think there are some missing DNS and RDNS settings for the mailing list Server. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Bind on virtual network interfaces
Am 18.11.2011 00:17, schrieb Ondrej Kuchár: I have in pdns.conf this line: local-address=xx.229.35.136 Pdns is listening on the right interface: # netstat -tulpn | grep pdns tcp0 0 94.229.35.136:530.0.0.0:* LISTEN 23837/pdns_server-i The problem occur when I made changes on master or notify slave dns with command. The notify is sendet from bad interface - not from the local-address. # pdns_control notify testdomain.com Have you already tried the option query-local-address= regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PDNS devel and weird IPv6 log entries
On Tue, 14 Jun 2011 16:49:33 +0200, Detlef Peeters wrote: O.K. I'll answering myself. ;) I've done some checks and the problem was with the ip6tables under CentOS 5. I've done som changes and now it' working. I've also done the check with the current pdns-static-3.0rc2.20110614.2216-1.i386.rpm and the zone transfer and update is working via IPv6. Today I notice the following log files during a zone update. Master Server (FreeBSD 8 Stable amd64 - powerdns-devel-20110529-2203): Jun 15 10:12:12 eka pdns[71532]: Queued notification of domain 'heringa.de' to 2a00:dd0:0:6::17 Jun 15 10:12:12 eka pdns[71532]: AXFR of domain 'heringa.de' initiated by 2a00:dd0:0:6::17 Jun 15 10:12:12 eka pdns[71532]: AXFR of domain 'heringa.de' to 2a00:dd0:0:6::17 finished Jun 15 10:12:13 eka pdns[71532]: Received spurious notify answer for 'heringa.de' from [2a00:dd0:0:6::17]:53 Jun 15 10:12:16 eka pdns[71532]: Received spurious notify answer for 'heringa.de' from [2a00:dd0:0:6::17]:53 Jun 15 10:12:21 eka pdns[71532]: Received spurious notify answer for 'heringa.de' from [2a00:dd0:0:6::17]:53 Jun 15 10:12:30 eka pdns[71532]: Received spurious notify answer for 'heringa.de' from [2a00:dd0:0:6::17]:53 Slave Server (CentOS 5.6 i386 - pdns-static-3.0rc2.20110614.2216-1.i386.rpm): Jun 15 10:12:12 net pdns[30420]: 1 slave domain needs checking, 0 queued for AXFR Jun 15 10:12:12 net pdns[30420]: Received serial number updates for 1 zones, had 0 timeouts Jun 15 10:12:12 net pdns[30420]: Domain heringa.de is stale, master serial 2011061501, our serial 2011061405 Jun 15 10:12:12 net pdns[30420]: Initiating transfer of 'heringa.de' from remote '2001:4d88:::d0:b723:6daf:2' Jun 15 10:12:12 net pdns[30420]: AXFR started for 'heringa.de', transaction started Jun 15 10:12:12 net pdns[30420]: Zone 'heringa.de' (/etc/powerdns/slave/heringa.de.zone) reloaded Jun 15 10:12:12 net pdns[30420]: AXFR done for 'heringa.de', zone committed Jun 15 10:12:15 net pdns[30420]: 1 slave domain needs checking, 0 queued for AXFR Jun 15 10:12:15 net pdns[30420]: Received serial number updates for 1 zones, had 0 timeouts Jun 15 10:12:15 net pdns[30420]: Domain heringa.de is fresh (not presigned, no RRSIG check) Jun 15 10:12:20 net pdns[30420]: 1 slave domain needs checking, 0 queued for AXFR Jun 15 10:12:20 net pdns[30420]: Received serial number updates for 1 zones, had 0 timeouts Jun 15 10:12:20 net pdns[30420]: Domain heringa.de is fresh (not presigned, no RRSIG check) Jun 15 10:12:29 net pdns[30420]: 1 slave domain needs checking, 0 queued for AXFR Jun 15 10:12:29 net pdns[30420]: Received serial number updates for 1 zones, had 0 timeouts Jun 15 10:12:29 net pdns[30420]: Domain heringa.de is fresh (not presigned, no RRSIG check) Jun 15 10:13:46 net clamd[6304]: SelfCheck: Database status OK. I'm wondering about the "spurious notify" in the log files. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PDNS devel and weird IPv6 log entries
On Tue, 14 Jun 2011 15:18:09 +0200, Detlef Peeters wrote: On Tue, 14 Jun 2011 11:55:14 +0200, bert hubert wrote: On Tue, Jun 14, 2011 at 11:21:45AM +0200, Detlef Peeters wrote: >Or to any of the slaves of depee.org ? Yes, IPv6 is enabled, and PowerDNS ist listening to it. The mater server for the domain depee.org has the IPv6 address: "2001:4d88:::d0:b723:6daf:2". With PowerDNS 2.9.22 and the same configuration I haven't seen this log entries. This is probably because PowerDNS 2.9.22 would not notify IPv6 hosts ;-) The error is very weird, could you tcpdump to see if the correct IP addresses are actually on the wire? Yes, the correct IPv6 address is on the interface. This log entry is not on each zone update. So it's not so easy to debug. I can also see the following new log entry: Jun 14 15:05:57 eka pdns[71532]: No question section in packet from 2a00:dd0:0:6::17, rcode=5 Jun 14 15:05:57 eka pdns[71532]: Unable to parse SOA notification answer from 2a00:dd0:0:6::17 The Server with the IP 2a00:dd0:0:6::17 has as DNS Server NSD 3.2.7 with IPv6 enabled and the zone is correct updated on the secondary. O.K. I'll answering myself. ;) I've done some checks and the problem was with the ip6tables under CentOS 5. I've done som changes and now it' working. I've also done the check with the current pdns-static-3.0rc2.20110614.2216-1.i386.rpm and the zone transfer and update is working via IPv6. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PDNS devel and weird IPv6 log entries
On Tue, 14 Jun 2011 11:55:14 +0200, bert hubert wrote: On Tue, Jun 14, 2011 at 11:21:45AM +0200, Detlef Peeters wrote: >Or to any of the slaves of depee.org ? Yes, IPv6 is enabled, and PowerDNS ist listening to it. The mater server for the domain depee.org has the IPv6 address: "2001:4d88:::d0:b723:6daf:2". With PowerDNS 2.9.22 and the same configuration I haven't seen this log entries. This is probably because PowerDNS 2.9.22 would not notify IPv6 hosts ;-) The error is very weird, could you tcpdump to see if the correct IP addresses are actually on the wire? Yes, the correct IPv6 address is on the interface. This log entry is not on each zone update. So it's not so easy to debug. I can also see the following new log entry: Jun 14 15:05:57 eka pdns[71532]: No question section in packet from 2a00:dd0:0:6::17, rcode=5 Jun 14 15:05:57 eka pdns[71532]: Unable to parse SOA notification answer from 2a00:dd0:0:6::17 The Server with the IP 2a00:dd0:0:6::17 has as DNS Server NSD 3.2.7 with IPv6 enabled and the zone is correct updated on the secondary. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PDNS devel and weird IPv6 log entries
On Tue, 14 Jun 2011 11:08:55 +0200, bert hubert wrote: On Tue, Jun 14, 2011 at 11:01:40AM +0200, Detlef Peeters wrote: Hello, I'm using the FreeBSD Port powerdns-devel-20110529-2203.tbz from http://www.cainites.net/files/powerdns/ After a domain update I can see the following log entries with a not correct IPv6 address. Do you actually run with IPv6 enabled? Is PowerDNS listening on IPv6? Is 2001:4d88 related to any IPv6 address you might have? Or to any of the slaves of depee.org ? Yes, IPv6 is enabled, and PowerDNS ist listening to it. The mater server for the domain depee.org has the IPv6 address: "2001:4d88:::d0:b723:6daf:2". With PowerDNS 2.9.22 and the same configuration I haven't seen this log entries. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] PDNS devel and weird IPv6 log entries
Hello, I'm using the FreeBSD Port powerdns-devel-20110529-2203.tbz from http://www.cainites.net/files/powerdns/ After a domain update I can see the following log entries with a not correct IPv6 address. Jun 14 10:53:30 eka pdns[71532]: Received unsuccessful notification report for 'depee.org' from [2001:4d88::::17]:53, rcode: 4 Jun 14 10:53:30 eka pdns[71532]: Received spurious notify answer for 'depee.org' from [2001:4d88::::17]:53 Where comes this IPv6 adress from? The FreeBSD IPv6 handling, or from PDNS? regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] New PowerDNS Authoritative Server snapshot with DNSSEC + Release Notes
Am 28.01.2011 22:15, schrieb bert hubert: > On Fri, Jan 28, 2011 at 07:28:16PM +0100, bert hubert wrote: >> On Fri, Jan 28, 2011 at 12:27:13AM +0100, Detlef Peeters wrote: >>> On 27.01.2011 23:37, bert hubert wrote: >>> >>>> (the short version, there is a snapshot worth looking at, packages on >>>> http://powerdnssec.org/downloads - documentation on http://powerdnssec.org >>>> ) >>> >>> I have upgraded to the snapshot on a CentOS5 i386 machine from 2.9.22 >>> and have a problem to resolve external domains via PowerDNS-Recursor. >>> I'm using the same configuration with PDNS 2.9.22 without problems. >> >> I can confirm this issue, apologies. The new DNSSEC code does not do >> Recursor handoff yet. > > And now it does, in snapshot 1928, tarballs & packages are online. Yes. It's working now. Thanks for fixing it. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] New PowerDNS Authoritative Server snapshot with DNSSEC + Release Notes
On 27.01.2011 23:37, bert hubert wrote: > (the short version, there is a snapshot worth looking at, packages on > http://powerdnssec.org/downloads - documentation on http://powerdnssec.org ) I have upgraded to the snapshot on a CentOS5 i386 machine from 2.9.22 and have a problem to resolve external domains via PowerDNS-Recursor. I'm using the same configuration with PDNS 2.9.22 without problems. When I try to resolve a hostname I can see the following log entries. pdns.conf: allow-recursion=127.0.0.1, 10.5.1.0/30 recursor=127.0.0.1:5300 command: user@negro: host powerdns.com Host powerdns.com not found: 2(SERVFAIL) log: 2011-01-28T00:22:18.371337+01:00 negro pdns[15099]: Remote 127.0.0.1 wants 'powerdns.com|A', do = 0, bufsize = 512: packetcache MISS 2011-01-28T00:22:18.371768+01:00 negro pdns[15099]: Remote 127.0.0.1 wants 'powerdns.com|A', do = 0, bufsize = 512: packetcache HIT Have I to change something in the configuration? regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS and DomainKeys Oddities
On 29.12.2010 19:32, Jeremy Utley wrote: > The problem: > > When I make DomainKeys entries, I'm getting backslashes in my output > from dig, but when looking at either the PowerAdmin interface or > directly at the MySQL data, I'm not seeing them. See below: > > Dig output: > ;; ANSWER SECTION: > _domainkey.domain.com. 41411 IN TXT "t=y\; o=-\;" Dig is adding quotes in the output around the record and adding backslashes before the semicolons and not PowerDNS. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns-recursor-3.3rc2 cache is growing slow
On Mon, 20 Sep 2010 11:00:58 +0200, Detlef Peeters wrote: > I've noticed on the machine I am testing pdns-recursor-3.3rc2 the > cache is growing really slow. After 6 days there are only 80.000 > entries. With pdns-recursor-3.2 the cache is filled up to 1.000.000 > entries after 5 days. > > Has there something changed with the cache handling in pdns-recursor-3.3rc2? O.K. Problem is solved. On the Testmachine there was in the "recursor.conf" a missing entry in the "allow-from=" parameter. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS Recursor 3.3-RC3 released
On Tue, 21 Sep 2010 11:16:57 +0200, bert hubert wrote: > On Tue, Sep 21, 2010 at 11:08:33AM +0200, Detlef Peeters wrote: >> On Mon, 20 Sep 2010 20:22:40 +0200, bert hubert >> wrote: >> >> > PowerDNS Recursor 3.3 Release Candidate 3 is now available! It is in wide >> > production use already, but we'd like everyone to take a good look at it >> > before we release it as 3.3-final. If nothing crops up, RC3 will be the >> > exact same as the 3.3 release. >> >> I've installed it today and I noticed the following message I've never >> seen before: >> >> Unable to parse packet from remote server 216.38.220.31: Error parsing >> packet of 123 bytes (rd=0), out of bounds: vector::_M_range_check > > Detlef, these messages are not new, but perhaps you should configure > 'log-dns-details=off'. > > The message means that the remote authoritative server 216.38.220.30 is > sending you malformed packets. Thank you for the fast answer. Is it the same option in the configuration as "log-common-errors"? regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] PowerDNS Recursor 3.3-RC3 released
On Mon, 20 Sep 2010 20:22:40 +0200, bert hubert wrote: > PowerDNS Recursor 3.3 Release Candidate 3 is now available! It is in wide > production use already, but we'd like everyone to take a good look at it > before we release it as 3.3-final. If nothing crops up, RC3 will be the > exact same as the 3.3 release. I've installed it today and I noticed the following message I've never seen before: Unable to parse packet from remote server 216.38.220.31: Error parsing packet of 123 bytes (rd=0), out of bounds: vector::_M_range_check Unable to parse packet from remote server 216.38.220.30: Error parsing packet of 123 bytes (rd=0), out of bounds: vector::_M_range_check What does it mean? regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns-recursor-3.3rc2 cache is growing slow
On Mon, 20 Sep 2010 13:17:06 +0300, Imre Gergely wrote: > On 09/20/2010 12:46 PM, Detlef Peeters wrote: >> On Mon, 20 Sep 2010 11:39:36 +0200, bert hubert >> wrote: >>> Odd - can you paste some 'stats:' lines from the log files? >>> >>> stats: 4331362754 questions, 1003788 cache entries, 100987 negative entries, >>> 27% cache hits >>> stats: throttle map: 2752, ns speeds: 76672 >>> stats: outpacket/query ratio 3205%, 2% throttled, 0 no-delegation drops >>> stats: 263614 outgoing tcp connections, 146 queries running, 45761180 >>> outgoing timeouts >>> stats: 504910 packet cache entries, 8798% packet cache hits >>> stats: 6286 qps (average over 1801 seconds) >>> >>> This is from our testing of rc1. >> >> Yes, >> >> here are some stats: >> >> stats: 155898 questions, 83540 cache entries, 1237 negative entries, >> 21% cache hits >> stats: throttle map: 2, ns speeds: 2371 >> stats: outpacket/query ratio 138%, 0% throttled, 0 no-delegation drops >> stats: 108 outgoing tcp connections, 1 queries running, 2483 outgoing >> timeouts >> stats: 24177 packet cache entries, 8% packet cache hits >> stats: 1 qps (average over 1916 seconds) > > Is this pdns 3.3-rc2 actually being used? Seems to me it's getting > really low traffic. Are these stats from the 3.3rc2 running for six days > straight? 155k questions would hardly fill up a cache of 1mil. Yes, these stats are from the 3.3rc2. Here are some old stats from the same server running with 3.2 installed: stats: 11844008 questions, 1000141 cache entries, 4347 negative entries, 10% cache hits stats: throttle map: 67, ns speeds: 3561 stats: outpacket/query ratio 102%, 0% throttled, 0 no-delegation drops stats: 1347 outgoing tcp connections, 7 queries running, 138758 outgoing timeouts stats: 500145 packet cache entries, 4% packet cache hits stats: 11 qps (average over 2015 seconds) regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns-recursor-3.3rc2 cache is growing slow
On Mon, 20 Sep 2010 11:39:36 +0200, bert hubert wrote: > Odd - can you paste some 'stats:' lines from the log files? > > stats: 4331362754 questions, 1003788 cache entries, 100987 negative entries, > 27% cache hits > stats: throttle map: 2752, ns speeds: 76672 > stats: outpacket/query ratio 3205%, 2% throttled, 0 no-delegation drops > stats: 263614 outgoing tcp connections, 146 queries running, 45761180 > outgoing timeouts > stats: 504910 packet cache entries, 8798% packet cache hits > stats: 6286 qps (average over 1801 seconds) > > This is from our testing of rc1. Yes, here are some stats: stats: 155898 questions, 83540 cache entries, 1237 negative entries, 21% cache hits stats: throttle map: 2, ns speeds: 2371 stats: outpacket/query ratio 138%, 0% throttled, 0 no-delegation drops stats: 108 outgoing tcp connections, 1 queries running, 2483 outgoing timeouts stats: 24177 packet cache entries, 8% packet cache hits stats: 1 qps (average over 1916 seconds) regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] pdns-recursor-3.3rc2 cache is growing slow
Hello, I've noticed on the machine I am testing pdns-recursor-3.3rc2 the cache is growing really slow. After 6 days there are only 80.000 entries. With pdns-recursor-3.2 the cache is filled up to 1.000.000 entries after 5 days. Has there something changed with the cache handling in pdns-recursor-3.3rc2? regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] pdns-recursor-3.3rc2 our root expired messages
On Wed, 15 Sep 2010 13:39:11 +0200, bert hubert wrote: > On Wed, Sep 15, 2010 at 01:37:30PM +0200, Detlef Peeters wrote: >> pdns_recursor[32068]: objects-test.deviantart.com.edgesuite.net.: >> our root expired, repriming from hints and retrying >> pdns_recursor[32068]: s.de.net.: our root expired, repriming from >> hints and retrying > Can you list the relevant parts of your configuration file? (ie, not > allow-from, local-address etc). > > Does this happen immediately? Or after a day? The only changes to the recursor.conf-dist file are -local-address=*** -setgid=pdns -setuid=pdns It happened after a day. I've installed and started the pdns-recursor at 2010-09-14T13:21:18 and the first entry was today at 2010-09-15T13:21:37 and the second at 2010-09-15T13:29:00 regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] pdns-recursor-3.3rc2 our root expired messages
Hello, today I notice in the logs following messages. pdns_recursor[32068]: objects-test.deviantart.com.edgesuite.net.: our root expired, repriming from hints and retrying pdns_recursor[32068]: s.de.net.: our root expired, repriming from hints and retrying Installed is pdns-recursor-3.3rc2-1.x86_64.rpm on CentOS 5.5 Is there a problem, or what does this messages means. regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Problem with PowerDNS Recursor 3.2 and EDNS enabled
On Thu, 01 Apr 2010, bert hubert wrote: > On Thu, Apr 01, 2010 at 12:09:12PM +0200, Detlef Peeters wrote: >> Hello, >> >> I've installed yesterday the Update to PowerDNS Recursor 3.2. In the >> config I've enabled EDNS with the option "disable-edns=no". > > You've discovered the (removed) EDNS support from PowerDNS. By mistake, > 'disable-edns' was not removed from the --help output. > > It is not documented, and it is is not supported (for now). The disable-edns > feature should not have been visible. > > That it works at all is a miracle ;-) Bert, thank you for your answer. The most name resolutions worked for me. The option "disable-edns=" is also in the "recursor.conf-dist" file. Now, I have removed it from the config and it's working fast and good, and without problems. > > When we try to reach "www.danskebank.dk" then there is no resolution to > > the IP. In the log I can see following entrys: > > > > pdns_recursor[3518]: Discarding unexpected packet from 192.42.93.33: , 0 > > pdns_recursor[3518]: Discarding unexpected packet from 192.35.51.33: , 0 > > pdns_recursor[3518]: Discarding unexpected packet from 192.41.162.33: , 0 > > pdns_recursor[3518]: Discarding unexpected packet from 192.5.6.33: , 0 > > EDNS support was disabled for this specific reason. It turns out that as a > nameserver, an inordinate amount of time and packets is spent on discovering > the sizeable number of servers that do not support EDNS, and in fact return > strange error packets. > > > Where is the problem? With the nameserver from Danskbank? Or is it better > > at the moment to disable EDNS in PowerDNS Recursor? > > Definitely. > > In the future, we might move to 'EDNS if really necessary', for example, > after receiving a truncated packet. Thank you for clarify it all. Best regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] Problem with PowerDNS Recursor 3.2 and EDNS enabled
Hello, I've installed yesterday the Update to PowerDNS Recursor 3.2. In the config I've enabled EDNS with the option "disable-edns=no". When we try to reach "www.danskebank.dk" then there is no resolution to the IP. In the log I can see following entrys: pdns_recursor[3518]: Discarding unexpected packet from 192.42.93.33: , 0 pdns_recursor[3518]: Discarding unexpected packet from 192.35.51.33: , 0 pdns_recursor[3518]: Discarding unexpected packet from 192.41.162.33: , 0 pdns_recursor[3518]: Discarding unexpected packet from 192.5.6.33: , 0 When I disable EDNS then it's working right. # host www.danskebank.dk www.danskebank.dk has address 212.93.34.226 Where is the problem? With the nameserver from Danskbank? Or is it better at the moment to disable EDNS in PowerDNS Recursor? Best regards, Detlef ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
