Re: [Pdns-users] PowerDNS needs your thoughts on two important DNSSEC matters

2012-09-06 Thread Peter van Dijk
Hello,

On Sep 4, 2012, at 20:50 , Peter van Dijk wrote:

 2. ALTER TABLE records ADD order name  VARCHAR(255) BINARY
  Then you don't care about the CHARSET used by the server. 
  This syntax always set the binary collation specific for that charset
 
 This is a good tip I did not know about. I will look into this. The downside 
 of VARBINARY is that queries also become case-sensitive, which is acceptable 
 for PowerDNS but makes debugging harder. Thanks!


This works just as well as VARBINARY, indeed. Sadly, it does also make queries 
case-sensitive. If anyone has a suggestion that avoids case-sensitivity, please 
let us know. Otherwise we will go with VARCHAR BINARY. 

Thanks!

Kind regards,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/

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


Re: [Pdns-users] publish SPF and TXT records?

2012-09-06 Thread Arsen STASIC
* Marc van de Geijn m...@bhosted.nl [2012-09-05 16:14 (+)]:
 According to rfc's the dns server should publish both spf and txt. We now 
 create the spf, but not the txt version of the same spf.

Hi Marc,

Just take into consideration the ongoing IETF discussion about
obsoleting SPF RR.

12.1.  The SPF DNS Record Type

   Per [RFC4408], the IANA assigned the Resource Record Type and Qtype
   from the DNS Parameters Registry for the SPF RR type with code 99.
   The format of this type is identical to the TXT RR [RFC1035].  The
   character content of the record is encoded as [US-ASCII].  Use of
   this record type is obsolete for SPF Version 1.

   IANA is requested to add an annotation to the SPF RRTYPE saying
   (OBSOLETE - use TXT) in the DNS Parameters registry.

   [NOTE TO RFC EDITOR: (to be changed to  ... has added ... upon
   publication)]

This is taken from the latest draft:
https://tools.ietf.org/wg/spfbis/draft-ietf-spfbis-4408bis/draft-ietf-spfbis-4408bis-06-from-05.wdiff.html

just my 2ct
-arsen
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] publish SPF and TXT records?

2012-09-06 Thread Leen Besselink
On Thu, Sep 06, 2012 at 02:35:13PM +, Marc van de Geijn wrote:
 Thanks, Arsen, for this information.
 
 Are there any statistics on the number of mailservers/... requesting SPF 
 records instead of TXT records?
 

I know some of the software on our mailservers doesn't even try SPF.

isc.org and ietf.org do publish both, but they seem to be the exception.

hotmail.com , gmail.com , sendmail.com and many others only have TXT and no SPF.

 -Oorspronkelijk bericht-
 Van: Arsen STASIC [mailto:arsen.sta...@univie.ac.at] 
 Verzonden: donderdag 6 september 2012 16:15
 Aan: Marc van de Geijn
 CC: Peter van Dijk; pdns-users Users
 Onderwerp: Re: [Pdns-users] publish SPF and TXT records?
 
 * Marc van de Geijn m...@bhosted.nl [2012-09-05 16:14 (+)]:
  According to rfc's the dns server should publish both spf and txt. We now 
  create the spf, but not the txt version of the same spf.
 
 Hi Marc,
 
 Just take into consideration the ongoing IETF discussion about obsoleting SPF 
 RR.
 
 12.1.  The SPF DNS Record Type
 
Per [RFC4408], the IANA assigned the Resource Record Type and Qtype
from the DNS Parameters Registry for the SPF RR type with code 99.
The format of this type is identical to the TXT RR [RFC1035].  The
character content of the record is encoded as [US-ASCII].  Use of
this record type is obsolete for SPF Version 1.
 
IANA is requested to add an annotation to the SPF RRTYPE saying
(OBSOLETE - use TXT) in the DNS Parameters registry.
 
[NOTE TO RFC EDITOR: (to be changed to  ... has added ... upon
publication)]
 
 This is taken from the latest draft:
 https://tools.ietf.org/wg/spfbis/draft-ietf-spfbis-4408bis/draft-ietf-spfbis-4408bis-06-from-05.wdiff.html
 
 just my 2ct
 -arsen
 ___
 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] Setting up PDNS in a DMZ

2012-09-06 Thread admin
Forgot to send to the list...

Just a suggesting, but if you're using mysql, you might want to look into mysql 
replication.

I use it on my servers instead of master/slave functionality and it works a 
treat. You also get the added benefit of instant updates.

I'd give it a go!

Oli
Sent from my BlackBerry® wireless device

-Original Message-
From: Nixon, Anthony S. asni...@midrex.com
Sender: pdns-users-boun...@mailman.powerdns.com
Date: Thu, 6 Sep 2012 20:50:40 
To: pdns-users@mailman.powerdns.compdns-users@mailman.powerdns.com
Subject: [Pdns-users] Setting up PDNS in a DMZ

Hello,

I have three PDNS 3.1 servers running on CentOS 6 with MySQL backends and 
PowerAdmin interfaces.  These are running on VMware 5.1.  I have them in a DMZ 
with a 172.20.1.X subnet and NAT'd to the world (internally and externally are 
seen as the outside address).  My problem is getting the slaves to update off 
of the master.  I have added the master to the slaves as the supermaster, but I 
get nothing.  No transfers at all.

If I manually add the zone, it populates once from the master, but then no 
other updates/transfers take place.  I have the correct IPs set up for notifies 
and transfers on the master to the slaves.  But changing a zone on the master 
does nothing.  Should I add the 172.20.1 zone to the servers?  I did have each 
set up in the hosts file with the DMZ addresses.  I currently use a BIND server 
inside to populate the servers, but I really don't want to go with that model.  
I would prefer to use PDNS for everything.  Any help would be appreciated.


-- Roxer
-
This message, including any attachments, is intended only for the use of the 
addressee and contains information that is PROPRIETARY and CONFIDENTIAL. It may 
be used only by the addressee and may not be divulged without the express 
consent of the sender. If you are not the intended recipient, you are hereby 
notified that any dissemination of this communication is strictly prohibited. 
If you have received this communication in error, please erase all copies of 
the message and its attachments and notify us immediately. Thank you.
___
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