<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Daniel &#8211; SoluteDNS</title>
	<atom:link href="https://www.solutedns.com/blog/author/daniel/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.solutedns.com</link>
	<description>PowerDNS Web Manager for WHMCS</description>
	<lastBuildDate>Sun, 16 Oct 2016 22:06:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.solutedns.com/wp-content/uploads/2015/12/cropped-EpqbbVF_-32x32.png</url>
	<title>Daniel &#8211; SoluteDNS</title>
	<link>https://www.solutedns.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Gain extra trust with DANE/TLSA</title>
		<link>https://www.solutedns.com/blog/1088/extra-trust-with-danetlsa/</link>
		
		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Sun, 16 Oct 2016 22:05:02 +0000</pubDate>
				<category><![CDATA[Insights]]></category>
		<category><![CDATA[assistant]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[dane]]></category>
		<category><![CDATA[dnssec]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[tlsa]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=1088</guid>

					<description><![CDATA[Encrypted connections are identified using certificates which are issued by certificate authorities (CA’s). In recent years a number of CA’s experienced security breaches causing certificates being issued for domains which are owned by others. Meanwhile DNSsec has become a standard which allows the DNS-based Authentication of Named Entities (DANE) to be used to verify the certificates validity. The DANE protocol allows X.509 certificates to be tied to DNS zones using the DNSsec extension. In RFC6698 this method has been proposed as a way to authenticate TLS entities without a certificate authority. In the current DNS protocol, DANE can be applied using the TLSA record. This record type is mostly used for web-certificates (HTTPS) and secure mail-transport (SMTP) and provides an extra trust anchor for the secured connection. The TLSA record contains information about the encryption protocol and the X.509 certificates fingerprint. The SoluteDNS TLSA Assistant can generate the fingerprint for you when providing an X.509 certificate. The most important parameter of the TLSA record is the usage parameter. The usage defines how the fingerprint should be validated. You have the following usage options: 0. PKIX-TA: Certificate Authority Constraint: Anchors a specified CA certificate in the chain of trust in addition to the normal certificate validation and must pass PKIX validation (Public-Key infrastructure). 1. PKIX-EE: Service Certificate Constraint: Anchors a specified server certificate in the chain of trust in addition to the normal certificate validation and must pass PKIX validation. 2. DANE-TA: Trust Anchor Assertion: Anchors a specified CA certificate in the chain of trust which will be considered to be the trust anchor. 3. DANE-EE: Domain Issued Certificate: Anchors a specified server certificate that requires to match the server certificate. &#160; Where usage 0 and 1 become an addition to the chain of trust, the usage 2 and 3 do not. Usage 2 and 3 operate independently of the TLS validation which makes these usages useful for self-signed certificates and clients which do not validate trust anchors like SMTP clients. Usage 0 and 1 however are capable of detecting differences between trust anchors in the chain of trust which makes these usages more secure. An example of a TLSA record: _443._tcp.dnssec.com 3600 IN TLSA 2 0 1 8310f548d4785f30c141aa7ab4b14af93435d867cac4bb938776dca2a5a0ae04 &#60;port&#62; &#60;protocol&#62; &#60;name&#62; 3600 IN TLSA &#60;usage&#62; &#60;selector&#62; &#60;type&#62; &#60;fingerprint&#62; The SoluteDNS TLSA assistant helps you in creating new TLSA records. If you want to obtain a X.509 certificate for your website you can do so by exporting the CA certificate from within your browser as X.509 certificate file. Most modern browsers allow you to export these certificates. A thing to consider when starting to use TLSA records is they do need maintenance. If the certificate is renewed the TLSA record needs to be rolled-over as well. Also check Common Dane Mistakes by Sys4.de. Here you can also check your SMTP servers for DANE. SIDNlabs offers a TLSA check for your website.]]></description>
		
		
		
			</item>
		<item>
		<title>The Second Branch</title>
		<link>https://www.solutedns.com/blog/866/the-second-branch/</link>
		
		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Wed, 07 Oct 2015 12:10:14 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[eol]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=866</guid>

					<description><![CDATA[A view months back WHMCS announced their new v6 release. We had to pull all stops in order to make SoluteDNS compatible with this new release and at the same time comply with our future development plans as resources are valuable. Beta Release On September 1st 2015 we released the first alpha of our new branch which is fully compatible with WHMCS v6. Today we are about to launch the beta release of this second branch of SoluteDNS. This new release v0.2.1 will be available on October 10th 2015. This new release contains many fixes and enhancements and comes with some new features. In our releases we are working hard to get to a release candidate. In this progress our business strategy also adapts to its developments. New Plans To make sure we are able to support and maintain SoluteDNS in a long term we have decided to drop the owned plans and introduce new leased plans. In our pricing model we have tried to create a solution for everyone from starting businesses to large enterprises. We even got a limited free plan. We fully understand much people would like to see an owned license plan, but we think we cannot provide qualitative long term support on these kind of licenses. End Of Life Wrapping up as WHMCS v5 will reach the end of life state at October 31th 2015 we strongly recommend SoluteDNS users to upgrade their WHMCS v5 setup to v6.1 when SoluteDNS v0.2.1 is released. Together with WHMCS we will also drop active support for our v0.1.x and below branch.]]></description>
		
		
		
			</item>
		<item>
		<title>A Developers update</title>
		<link>https://www.solutedns.com/blog/723/a-developers-update/</link>
		
		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Wed, 22 Apr 2015 22:26:15 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Alpha]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[Blesta]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=723</guid>

					<description><![CDATA[SoluteDNS is in beta for quite some while now and still the end of the beta doesn’t seem to be near. Since WHMCS has announced their next major release being V6 we have planned to move SoluteDNS to it’s next branch. As we expected WHMCS 6 broke our current release. Not beyond fixable but considering we wanted to bring our Blesta version code more closer to the WHMCS version code to make future updates easier we have decided to continue on our new core and create the SoluteDNS 0.2.x branch. Speaking about Blesta, indeed we are working on a release for Blesta! The core for our Blesta release was already designed and development already begun. For now we have taken this core to the new WHMCS branch and have reallocated our resources to WHMCS. Basically meaning our next release will be the 0.2.0 version of SoluteDNS which will be compatible with WHMCS 6. We do not intend to make it backwards compatible with older version of WHMCS. We will however continue support for the 0.1.x branch until WHMCS drops support for their current stable release (WHMCS 5). Development of the 0.2.x branch is still in an early stage but we are working hard to make sure SoluteDNS is available on WHMCS 6 as soon as possible. The initial release will be an alpha version. Depending on our users feedback we will decide if we are going forward with the beta on the second release or remain at alpha. As soon the 0.2.x branch for WHMCS is up and going we will move back to the Blesta development. We are excited to show you what we have done so far but we still need to wait a little longer as development is still in an early stage. If you have any questions about SoluteDNS please do not hesitate to contact our customer support!]]></description>
		
		
		
			</item>
		<item>
		<title>A year SoluteDNS</title>
		<link>https://www.solutedns.com/blog/596/a-year-solutedns/</link>
		
		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Fri, 01 Aug 2014 21:30:33 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[anniversary]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[solutedns]]></category>
		<category><![CDATA[v0.1.5]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=596</guid>

					<description><![CDATA[This month it is a year ago SoluteDNS was firstly released to the public. Since the first release a lot of improvements have been made including smaller usability features and bigger features like DNSsec management. In the upcoming release we have planned even more new features, including some who are requested allot by our user base. We are quite excited about the v0.1.5 release. As development will continue, SoluteDNS will evolve in its way to be one of the most advanced DNS Management solutions available.]]></description>
		
		
		
			</item>
		<item>
		<title>SoluteDNS Open Beta</title>
		<link>https://www.solutedns.com/blog/109/beta-testing/</link>
		
		<dc:creator><![CDATA[Daniel]]></dc:creator>
		<pubDate>Fri, 19 Jul 2013 12:37:57 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[solutedns]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=109</guid>

					<description><![CDATA[As part of the SoluteDNS development roadmap an public beta testing period has been issued. In the beta period everyone is able to test SoluteDNS for WHMCS for FREE without any obligations. End date Currently the public beta end date is not set. As soon the end date is known we will communicate this with our beta testers. Beta testers will be able to continue using SoluteDNS Beta for at least 2 months after the public beta has been closed. How to apply? Please click here for the submission form in order to apply for the beta program. Please note: The beta version is not meant for production environments, it is not recommended to use this software on live servers. The beta program is free of charge, you are not obligated for purchase during the beta period. Beta submissions are reviewed by hand, we intend to send your beta license within 24 hours.]]></description>
		
		
		
			</item>
	</channel>
</rss>
