Bert,
bert hubert wrote:
> Resolvers rarely if ever send out AA=1 answers. If you literally want to
> forward packets, dnsdist may be a better choice.
>
> Is the current behaviour causing you problems? If so can you tell us about
> those problems?
I can probably use dnsdist (I only just learne
d it make sense to leave
the AA bit alone when forwarding back authoritative responses? If not, why not?
-Julian Mehnle
signature.asc
Description: Message signed with OpenPGP
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.po
I wrote:
> The problem is that while a TXT record can contain multiple "strings"
> (the parts you have to enclose in double quotes in TXT records in both
> BIND and PowerDNS), each string can only be 256 bytes long at maximum
> by design -- one length octet plus 255 bytes of text (RFC 1035). If
>
Augie Schwer wrote:
> PowerDNS returns a malformed response when queried for a TXT record
> larger than 257 characters.
>
> [...]
>
> PowerDNS returns NOERROR and returns as much data as it can which ends
> up creating the corrupt packet.
>
> Admittedly one shouldn't put bad data in (the above re
Leen Besselink wrote:
> You can also see that here:
>
> http://doc.powerdns.com/changelog.html
>
> I'm unsure about what it does mean though.
>
> My first thought would be that it's code to split large TXT-records
> over different TXT-records.
>
> Or just that multi TXT-records didn't work at all,
shion wrote:
> Now I have added a SPF record.
> SPF v=spf1 -all
>
> [...]
>
> After adding a SPF record, it isn't possible to dig the domain.
Unlike others in this thread have said, "SPF" is very well a valid RR
type. Your problem is that you forgot to enclose the RR contents in
double quote
marty wrote:
> The SPF rr is still not very well supported and few servers support it.
> Dig seems to bork the SPF type pretty badly.
> [...]
> PDNS seems to serve this record, but I get a mess when I try to access
> it with dig. Otherwise, other compatable testing tools said it was
> working and v
bert hubert wrote:
> Daniel wrote:
> > is pdns able to handle IN SPF records?
>
> Yes. But be aware, it needs the data to be between "quotes" in the
> database.
However, if I understood your recent comment correctly:
> There is specific support in PowerDNS to either support bare TXT
> records, or
bert hubert wrote:
> On Thu, Sep 20, 2007 at 07:23:44PM +0000, Julian Mehnle wrote:
> > all of a sudden, I am having trouble with TXT or SPF records in
> > PowerDNS 2.9.21 (on Debian). I repeatedly get the following errors
> > in syslog:
>
> Do you use the debian
Julian Mehnle wrote:
> all of a sudden, I am having trouble with TXT or SPF records in
> PowerDNS 2.9.21 (on Debian). I repeatedly get the following errors in
> syslog:
Oh, and I'm using the gpgsql backend, in case this is relevant.
Julian.
signature.asc
Description: This
Hi all,
all of a sudden, I am having trouble with TXT or SPF records in PowerDNS
2.9.21 (on Debian). I repeatedly get the following errors in syslog:
| Sep 20 19:11:22 io pdns[24094]: Exception: Parsing record content: Data field
in DNS should start with quote (") at position 0 of 'v=spf1 op=au
Jens U. Gruschwitz wrote:
> my question - are there any explanations or examples out there how to
> implement SPF records in powerDNS? I haven't found anything in the pdns
> manual or the list archive
You should either publish a TXT record only, or both TXT and SPF (type 99)
records. PowerDN
bert hubert wrote:
> Somewhere in the coming 2 weeks, we will release the PowerDNS
> Authoritative Server version 2.9.21.
>
> [...]
>
> However, since so much has been changed, care should be taken when
> deploying 2.9.21.
>
> To signify the magnitude of the underlying improvements, the next
> rele
Hi all,
I'm having trouble making AXFRs to my authoritative PDNS server via IPv6:
| $ dig AXFR mehnle.net @::1
| ; <<>> DiG 9.3.2-P1 <<>> AXFR mehnle.net @::1
| ; (1 server found)
| ;; global options: printcmd
| ; Transfer failed.
| $ dig AXFR mehnle.net @2001:608:5::2
| ; <<>> DiG 9.3.2-P1 <<>>
Matt Cooling wrote:
> I would like to install both the PowerDNS authoritative server and the
> PowerDNS recursor on the same server. Is there any documentation which
> explains how to do this? If I try and install both RPMs I get a conflict
> message:
>
> file /usr/sbin/pdns_recursor from install o
Ian Tester wrote:
> Julian Mehnle <[EMAIL PROTECTED]> wrote:
> > Case insensitivity applies only to ASCII characters. So where's the
> > problem?
>
> We don't know if the data is ASCII. If what Bert stated is true, we
> don't know what the data sh
bert hubert wrote:
> On Sun, Dec 17, 2006 at 12:48:08AM +0000, Julian Mehnle wrote:
> > > It also requires some work on the database side of things, as for
> > > example PostgreSQL is fond of interpreting 'VARCHARs' as UTF-8,
> > > which a random label v
bert hubert wrote:
> On Sat, Dec 16, 2006 at 10:37:05PM +0100, Stephane Bortzmeyer wrote:
> > IDN is mandatory for host names but should not be for domain names
> > without hosts.
>
> People generally use DNS for host names these days.
>
> However, I'll make sure we'll remove this restriction in du
bert hubert wrote:
> To encode utf-8 domains so that they work, use 'IDN'.
>
> See: http://en.wikipedia.org/wiki/Internationalized_domain_name
I knew that, thanks. That's NOT what I'm trying to do.
> > Is there a way for serving domains with binary labels with PDNS? As
> > far as I can see, thi
Hi all,
I am having problems with getting the PowerDNS authoritative server to
serve domains that have binary labels. For instance, I have a domain with
an UTF-8 encoded label: "こんにちは.mehnle.net".
It works fine with BIND 9.3:
| $ dig @localhost こんにちは.mehnle.net
|
| ; <<>> DiG 9.3.2-P1 <<>
Augie Schwer wrote:
> On 12/7/06, Julian Mehnle <[EMAIL PROTECTED]> wrote:
> > I'd like to see a new release, too. Especially due to the broken SPF
> > RR-type support in the current release version.
>
> Out of curiosity does that mean you are running out of th
Augie Schwer wrote:
> The authoritative PowerDNS server has not had a release in quite some
> time, but I am seeing some pretty handy fixes and a lot more recent
> development in the trunk; am I way out of date if I am running a
> tagged release in production? Is everyone just running out of the
>
Michael Loftis wrote:
> SPF is simply a specially formatted TXT record associated with the
> sending domain which states which A, MX, or IP's can send mail on behalf
> of that domain. If you've got people denying mail because of no SPF
> record well you don't want to send mail to them anyway. SPF
Richard Vernooij wrote:
> I seem to have a problem that many messages from a webserver, or
> emailserver do not arrive on certain places.
>
> Now i found that it could be the reason, that i do not have SPF records
> for reverse DNS.
SPF has _nothing_ to do with reverse DNS.
> Now when i check
> h
Alex van den Bogaerdt wrote:
> I downloaded the RPM, started configuring the program and,
> as suggested, tried testing my install.
>
> Added to pdns.conf:
> launch=bind
> bind-example-zones
>
> PowerDNS 2.9.20 (C) 2001-2006 PowerDNS.COM BV (Mar 15 2006, 19:32:45,
> gcc 4.0.2) starting up
>
> tried
Matt Cooling wrote:
> I have just installed PowerDNS 2.9.20-1 on a test Linux server running
> Fedora 5. As per the documentation, the only entries in pdns.conf are:
> ---
> launch=bind
> bind-example-zones
> ---
> When I try to test the service I get
bert hubert wrote:
> On Fri, Aug 25, 2006 at 07:33:54PM +0000, Julian Mehnle wrote:
> > Let me guess, you are using MySQL?
>
> This is the PowerDNS mailing list, not the 'flame MySQL to death' list.
I apologize if my statements came over as "MySQL death flames&quo
Mark Martin wrote:
> Julian Mehnle wrote:
> > [...]
> > If your RDBMS supports views, you can store IP addresses in integer
> > format and generate the data required by PowerDNS on the fly from
> > that. Or you could make custom SQL queries in PDNS to do the same.
>
Mark Martin wrote:
> This is trivial in the scheme of things, but, would it be possible to
> include in the db record, the decimal of the IP address? This would
> enable front end providers to 'order' the ip addresses in the forward
> records, and better suits the db (i.e. a key).
Let me gues
Leon de Jager wrote:
> Just checked database for any weird types and there are none. The only
> types are:
>
> A
> NS
> CNAME
> MX
> SOA
> TXT (SPF)
>
> We have SPF records for our domain, but they are normal TXT records
Then I have no idea where the error comes from. Sorry.
I once tried to add
Leon de Jager wrote:
> I am running PowerDNS 2.9.17 on Debian and every few days the DNS server
> stops responding, with the following in the logs:
>
> Aug 10 15:05:45 fzns3 pdns[24620]: Unable to insert a record of type #0
> for 'domain.com'
> Aug 10 15:06:17 fzns3 pdns[24622]: Unable to insert a
31 matches
Mail list logo
