<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — Authenticating a Dynamic DNS server]]></title>
		<link>https://www.wolfssl.com/forums/topic1797-authenticating-a-dynamic-dns-server.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1797.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Authenticating a Dynamic DNS server.]]></description>
		<lastBuildDate>Wed, 01 Sep 2021 13:15:35 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Authenticating a Dynamic DNS server]]></title>
			<link>https://www.wolfssl.com/forums/post6252.html#p6252</link>
			<description><![CDATA[<p>Does your application call `wolfSSL_check_domain_name`? Verifying the common name in the cert is fine, but not necessary if you also have a trusted CA that signed the server&#039;s certificate.</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Wed, 01 Sep 2021 13:15:35 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6252.html#p6252</guid>
		</item>
		<item>
			<title><![CDATA[Re: Authenticating a Dynamic DNS server]]></title>
			<link>https://www.wolfssl.com/forums/post6235.html#p6235</link>
			<description><![CDATA[<p>Yes, we are using a pre-shared key cert and public key.<br />How does using a CA solves this problem?</p>]]></description>
			<author><![CDATA[null@example.com (gilo)]]></author>
			<pubDate>Sat, 28 Aug 2021 08:08:03 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6235.html#p6235</guid>
		</item>
		<item>
			<title><![CDATA[Re: Authenticating a Dynamic DNS server]]></title>
			<link>https://www.wolfssl.com/forums/post6222.html#p6222</link>
			<description><![CDATA[<p>Hi Gil,</p><p>Are you using a pre-shared key cert or public key for the authentication? You could use a CA that signs any new broker&#039;s cert to allow the clients to verify the new broker&#039;s cert.</p><p>Thanks,<br />Eric @ wolfSSL Support</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Fri, 27 Aug 2021 13:04:26 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6222.html#p6222</guid>
		</item>
		<item>
			<title><![CDATA[Authenticating a Dynamic DNS server]]></title>
			<link>https://www.wolfssl.com/forums/post6221.html#p6221</link>
			<description><![CDATA[<p>Hi,</p><p>Our company uses a wolfMQTT together with wolfSSL on a pic32 embedded client to communicate with a third party MQTT broker let&#039;s call it &quot;domain1&quot;.</p><p>The pic32 client has &quot;domain1&quot; server certificate planted within the code and wolfSSL_check_domain_name() function is called to authenticate the domain. The connection is secured and is working great.</p><p>While the pic32 MQTT clients are being scattered in customer&#039;s sites all over the world, it might happen that this third party MQTT broker would not be reliable anymore.</p><p>In order to solve this possible problem, we decided to create a middle-way dns record (let&#039;s call it &quot;domain2&quot;) in our private server that points to the dns of whatever MQTT broker that will be used in the future (currently &quot;domain1&quot; but can be &quot;domain3&quot; in the future) - like a lined list (-: .</p><p>Currently we tried changing the wolfMQTT &quot;DEFAULT_MQTT_HOST&quot; from pointing to good old &quot;domain1&quot; to pointing the middle-way DNS record &quot;domain2&quot; and it does not connect. I guess its because the pre-planted server certificate certificate still has &quot;domain1&quot; in it.</p><p>The question is: what server certificate (and its domain) is require to pre-plant inside the pic32 MQTT client in order to communicate with every possible domain that will be pointed by &quot;domain2&quot;(i believe this is called dynamic DNS)?</p><p>Thanks in advanced,</p><p>Gil</p>]]></description>
			<author><![CDATA[null@example.com (gilo)]]></author>
			<pubDate>Fri, 27 Aug 2021 08:01:54 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6221.html#p6221</guid>
		</item>
	</channel>
</rss>
