<?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>SoluteDNS</title>
	<atom:link href="https://www.solutedns.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.solutedns.com</link>
	<description>PowerDNS Web Manager for WHMCS</description>
	<lastBuildDate>Tue, 09 Oct 2018 21:37:23 +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>SoluteDNS</title>
	<link>https://www.solutedns.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>PowerDNS 3.x End of life statement</title>
		<link>https://www.solutedns.com/blog/1403/powerdns-3-x-end-of-life-statement/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Tue, 09 Oct 2018 21:37:23 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[PowerDNS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1403</guid>

					<description><![CDATA[PowerDNS declared the Authoritative Server 3.x used by SoluteDNS End of Life back in December 2017. Since we integrated support for the 4.x branch we left the 3.x support Authoritative Server support in place. Per January 1st 2019 we will stop supporting the 3.x Authoritative Server in our solutions. Up to January 1st 2019 we may no longer take into account the 3.x Authoritative Server branch for bug fixes, enhancements and new features. After January 1st 2019 we will gradually start removing support. If you are still using the 3.x branch please follow these instructions to upgrade to version 4.1 of the PowerNDS Authoritative Server.]]></description>
		
		
		
			</item>
		<item>
		<title>PHP Supported Versions 5.6/7.0 EOL</title>
		<link>https://www.solutedns.com/blog/1395/php-supported-versions-5-6-7-0-eol/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Mon, 27 Aug 2018 14:02:29 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1395</guid>

					<description><![CDATA[As you may be aware of PHP has announced the end of life for PHP 5.6 and 7.0 at December 31th 2018 and December 3th 2018. As our normal policy is to copy support plans of our vendors this will impact our system requirements as well. As per January 1st 2019 we will stop supporting PHP 5.6 and PHP 7.0 meaning new releases in 2019 and upcoming will no longer contain support for these PHP version. For our open source releases the impact may not be as severe as for our paid modules. These modules will no longer be encoded for older PHP versions meaning new releases after January 1st 2019 can only be used in PHP 7.1 and later. If you are still using one of the deprecated versions please make sure you are ready to upgrade before these PHP version reach end of life.]]></description>
		
		
		
			</item>
		<item>
		<title>Professional Edition for WHMCS</title>
		<link>https://www.solutedns.com/blog/1356/professional-edition-for-whmcs/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Sun, 06 May 2018 22:01:59 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[Professional Edition]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1356</guid>

					<description><![CDATA[We are happy to announce the beta release of SoluteDNS for WHMCS Professional Edition. The Professional Edition is a rewrite of the legacy WHMCS module in the structure of the earlier released Community Edition and fully utilises the SoluteDNS Core. Community Edition vs Professional Edition You where probably used to the: Lite, Starter, Standard and Premium plans. Now the Community and Professional editions are available these plans are no longer here. In general if you have a Lite or Starter plan your best bet is the Communiy Edition. If you have any other plan your best of with the Professional Edition. You can compare both plans here. Improvements The new Professional Edition comes with some changes and improvements compared to the old legacy module. Some of these changes are: The Template system and handling has been revised to make it more easier to configure. To use dynamically assigned IP’s you can now use the {ip} and {ip&#124;127.0.0.1} tags. The last tag including an IP address which acts as a default fallback IP address. If no IP can be found and no fallback IP has been set no records is added. The system now automatically adds multiple records when multiple assigned IP’s have been found for both IPv4 and IPv6. Regarding to tags in templates the old domain identifier tag &#60;domain&#62; has been changed to {domain}. When you save a domain or product in WHMCS, SoluteDNS will now check if the index is still up to date to avoid wrong assignments. Date conversion now applies the in WHMCS configured default format. The client e-mail address shown on the admin DNS Management page now redirects to opening a new ticket instead of opening the local mail client. Empty non terminal records are now hidden for both admin and clients. The message system has been updated to allow multiple messages at the same time through the same channel. The Staff Access management has been simplified to allow one admin group for full access. All other groups which have module access as configured in WHMCS are only able to performe DNS management operations and cannot change any settings. You can now add and select a different template to avoid customisations being overwritten when a automated update is being performed. Upgrading As the new module comes with quit some changes, upgrading through the auto updater has been disabled. You can download and upload an updater scripts which first prepares your database for the Professional Edition module. When done it will attempt to remove old files and install the new Professional Edition module. If you decide to go with the Community Edition we recommend to uninstall the current module and afterwards activate the Community Edition as fresh installation. Developers The Professional Edition uses the SoluteDNS Core which means all DNS operations can be called using the SoluteDNS Core API. For local operations there is an System API which helps to clear zone information locally or for example applying an locally created template to a zone. If you have made any customization we strongly advise to review this code as it&#8217;s most likely you have to update this code as well. Deprecated Functionality Some functionality has been deprecated in this new release. All SoluteDNS crons have been removed. We are now fully relying on the WHMCS system cron which makes installation and maintenance easier. The Local API has been removed in favour of the Core and System API’s. Please review the documentation of both the Professional Edition addon and SoluteDNS Core to update your customisations. The CLI tool has been removed since SoluteDNS now allows you to call (custom) script directly from the CLI. The Multi Master/Cluster functionality has also been deprecated as it was hardly used and caused too much hassle in maintaining SoluteDNS. &#160; We are eager to start this new chapter in the SoluteDNS books. If you have any feedback please do not hesitate to contact us!]]></description>
		
		
		
			</item>
		<item>
		<title>Community Edition for WHMCS</title>
		<link>https://www.solutedns.com/blog/1275/community-edition-for-whmcs/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Tue, 14 Nov 2017 12:58:13 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Community Edition]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1275</guid>

					<description><![CDATA[After the release of the SoluteDNS Core we are pleased to announce the release of the new SoluteDNS Community Edition for WHMCS. The Community Edition is a new free tier which has all basic features needed for DNS Mangement. The Community Edition is open source and comes as pre-packed version and as git at GitHub. When using the git the SoluteDNS Core has to be downloaded separately. Since the release of the SoluteDNS Core we are working towards integrating the Core in all of our products. We are pleased the Community Edition is the first product to embrace our DNS management Core. The SoluteDNS Core is available free of charge up to 25 zones to get you started. If you require more zones you can obtain an Core license. The Community Edition is fully editable as it uses Smarty template files, language files and is open source. Developers can use the full API suite of the SoluteDNS Core for DNS Mangement tasks to create an solution which fully fits your needs. Our 3.0 branch for SoluteDNS for WHMCS is on the way for users wo want more functionality as premade solution. The 3.0 branch will be our premium addon solution for WHMCS. Keep an eye out for more news.]]></description>
		
		
		
			</item>
		<item>
		<title>The Core is here</title>
		<link>https://www.solutedns.com/blog/1150/the-core-is-here/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Mon, 18 Sep 2017 14:13:10 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Community Edition]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1150</guid>

					<description><![CDATA[Ever since SoluteDNS has been released we always recognized the importance of customisation for our clients. We introduced several developer features over time to make this possible and committed to further improve and extend these options. Lately our attentions has gone to further improving the customizability of SoluteDNS even further. Today we have taken this functionality to the next level. We are eager to announce the SoluteDNS Core, which is the new engine behind all DNS Management features. The new SoluteDNS Core is an stand-alone product for developers which has over 25 callable actions to help integrate DNS Management in a comprehensive way into your own PHP system. We will start using the new SoluteDNS Core for our own integrations as well. The current known Internal API will be removed in favor of the new SoluteDNS Core. The SoluteDNS Core also introduces new license plans. Future integrations will become addons of the Core license. Speaking of those new integrations. Keep an eye on our blog as we will soon tell you more about our new open source Community Edition for WHMCS which will replace the current Lite and Starter licenses. The SoluteDNS Core is now available and can be downloaded from our forum. You can try the SoluteDNS Core free of charge as the first 25 zones are on us!]]></description>
		
		
		
			</item>
		<item>
		<title>Version 2.17.001 released</title>
		<link>https://www.solutedns.com/blog/1134/version-2-17-001-released/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Tue, 24 Jan 2017 17:08:49 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[solutedns]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">https://www.solutedns.com/?p=1134</guid>

					<description><![CDATA[We are pleased to release SoluteDNS for WHMCS v2.17.001. In this article we will shortly talk about this new update. For detailed changes please see the changelog and project tracker. You can review our GitHub page for template specific changes. Download &#124; Changelog Bug fixes This release contains several bug fixes related to license expiry issues, database upgrading issues, DNS type system wide availability, CSS and DataTables pagination. New version numbering In the light of our new distribution scheme the version numbering is now depending on the distribution instead of the old versioning system. The new version numbering exists of: &#60;branch&#62;.&#60;year&#62;.&#60;distribution&#62;. Local database back-end The database back-end for local database connections now fully use the WHMCS database handler. DatTables update DataTables has been updated to the latest version. Newsletter If you want to receive our newsletter about SoluteDNS please subscribe here.]]></description>
		
		
		
			</item>
		<item>
		<title>Version 0.2.7 released</title>
		<link>https://www.solutedns.com/blog/1128/version-0-2-7-released/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Fri, 16 Dec 2016 19:11:27 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[solutedns]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=1128</guid>

					<description><![CDATA[We are pleased to release SoluteDNS for WHMCS v0.2.7. In this article we will shortly talk about this new update. For detailed changes please see the changelog and project tracker. You can review our GitHub page for template specific changes. Download &#124; Changelog WHMCS v7.1 compatibility This new release of SoluteDNS is compatible with the newly released WHMCS v7.1 DNSsec improvements When allowed by the administrator clients can now enable or disable DNSsec for their zones.  We also improved DNSsec processing times during zone creation and the system now automatically rectifies a zone when NSEC3 is enabled by an admin. Internal API DNS cluster When licensed you can now pre-set the DNS cluster on which the zone should be created when using the internal API. Newsletter If you want to receive our newsletter about SoluteDNS please subscribe here.]]></description>
		
		
		
			</item>
		<item>
		<title>Version 0.2.6 released</title>
		<link>https://www.solutedns.com/blog/1106/version-0-2-6-released/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Thu, 27 Oct 2016 22:26:14 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[hooks]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[solutedns]]></category>
		<category><![CDATA[tlsa]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=1106</guid>

					<description><![CDATA[We are eager to announce the release of SoluteDNS for WHMCS v0.2.6. We will shortly talk about some highlights and changes in this new release. For detailed changes please see the changelog and project tracker. You can review our GitHub page for template specific changes. Download &#124; Changelog System requirements The minimum required version of PHP is 5.6 or higher. SoluteDNS is now encoded to support PHP 7 installations. WHMCS v7 is supported as well. New TLSA DNS Assistant The new TLSA DNS Assistant will help in creating new TLSA records. It can convert x.509 certificates to make life easier. DNS Health for Standard plans The DNS Health system is now available for standard plans as well. New hook points We have added an AfterZoneCreation hookpoint and a WHMCS menu entries hookpoint to this release which allows you to customize the automatically added menu entries. Custom client area URL You can now customize the client area link using the URL rewrite option. Newsletter If you want to receive our newsletter about SoluteDNS please subscribe here.]]></description>
		
		
		
			</item>
		<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>Version 0.2.5 released</title>
		<link>https://www.solutedns.com/blog/1050/version-0-2-5-released/</link>
		
		<dc:creator><![CDATA[SoluteDNS]]></dc:creator>
		<pubDate>Sun, 07 Aug 2016 22:00:26 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[release]]></category>
		<category><![CDATA[solutedns]]></category>
		<category><![CDATA[v0.2.5]]></category>
		<category><![CDATA[WHMCS]]></category>
		<guid isPermaLink="false">http://www.solutedns.com/?p=1050</guid>

					<description><![CDATA[We are excited to announce the release of SoluteDNS for WHMCS v0.2.5. In this article we will shortly highlight the changes in this new release. Please see the changelog, and project tracker for detailed information. For specific template changes you can review the GitHub page. Download &#124; Changelog Zone Import and Export The zone import and export options where previously only available for premium licenses. We have made this option available for standard licenses as well in this release. Languages Added We have added: German, Italian and Spanish language packs to the distribution package. WHMCS v7 compatibility WHMCS v7 compatibility has been reviewed. SoluteDNS v0.2.5 and later is compatible with WHMCS v7. Please do note SoluteDNS is currently not encoded for PHP 7 installations. PowerDNS v4 DNSsec support You can now also manage DNSsec with the all new PowerDNS v4 authoritative nameservers. Please do note the way SoluteDNS saves algorithm types has changed which may affect your customizations. SoluteDNS now passes the integer value of the algorithm instead of the written value. Improved product handling SoluteDNS now allows you to enable product specific settings. You can setup per product if DNSsec should be enabled, the record limit and the cluster in which the product zone should be created. Please note options availability may defer depending on your license. Automated updater security We have improved the security of the update package. New security measures will be applied on the next automated update release. The automated updater will still only update SoluteDNS when initiated manually. Health system cron The health system now has a separate cron which can be performed to do a global health check on all regular zones to determine issues quicker even when a zone is not updated for some while. See the health system documentation for more information about how to activate this cron job. System requirements changes The next release of SoluteDNS will have the following system requirements changes: - PHP 5.6 or later - WHMCS 6.3 or later - IonCube 5.0.1 or later - PHP_cURL Enabled For IDN support PHP_intl should also be enabled. Newsletter If you want to receive our newsletter about SoluteDNS please subscribe here.]]></description>
		
		
		
			</item>
	</channel>
</rss>
