Re: [Pdns-users] Standardized DNS Record Types Not Supported by PowerDNS

2015-03-09 Thread Nick Williams
On Mar 9, 2015, at 2:42 AM, bert hubert wrote: Sounds like the Supported Record Types page needs updating to add KX and IPSECKEY. Patches are welcome. It is very easy to update our Markdown documentation these days. https://github.com/PowerDNS/pdns/blob/master/docs/markdown/types.md

Re: [Pdns-users] Standardized DNS Record Types Not Supported by PowerDNS

2015-03-09 Thread Aki Tuomi
On Mon, Mar 09, 2015 at 12:00:52PM -0500, Nick Williams wrote: On Mar 9, 2015, at 2:42 AM, bert hubert wrote: Sounds like the Supported Record Types page needs updating to add KX and IPSECKEY. Patches are welcome. It is very easy to update our Markdown documentation these

Re: [Pdns-users] SOA and trailing/terminating dots (.)

2015-03-09 Thread Jan-Piet Mens
(and here comes a ticket, I think ) Ignore that, please: I pasted a wrong mysql query which explains the discrepancy in the SOA serial number; all else is ok, though. (It was a long day, sorry.) -JP ___ Pdns-users mailing list

Re: [Pdns-users] SOA and trailing/terminating dots (.)

2015-03-09 Thread Jan-Piet Mens
Here I'm particularly concerned with the part about SOA records. The instructions to never terminate the names in the SOA with a trailing dot (.) are counter to the instructions for every other DNS software and platform I can find, and counter to every about page/tutorial I can find for SOA

[Pdns-users] Standardized DNS Record Types Not Supported by PowerDNS

2015-03-09 Thread bert hubert
Sounds like the Supported Record Types page needs updating to add KX and IPSECKEY. Patches are welcome. It is very easy to update our Markdown documentation these days. https://github.com/PowerDNS/pdns/blob/master/docs/markdown/types.md and press the edit (pencil) icon. To bad about

Re: [Pdns-users] Master server not notifying slave (syslog included)

2015-03-09 Thread Melvin Mughal
Bert, you were spot on. One of the NS hostnames wasn't resolving properly and that got it fixed. The only thing that was a bit surprising is that the log was in both cases telling me that the binlog_format was set to statement and had issues with it. I fixed that by permanently setting