<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/8/2016 3:56 PM, Mythtv -
SIlicondust wrote:<br>
</div>
<blockquote
cite="mid:CAA0aiq-krNP7=3cTodzhgZ3nuRye8QGEwA0e32w5ncWgxcs1rA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Nov 8, 2016 at 3:17 PM, Gary
Buhrmaster <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On Tue, Nov 8, 2016 at
10:38 PM, Mike's JdJ <<a moz-do-not-send="true"
href="mailto:stepsisters@comcast.net">stepsisters@comcast.net</a>>
wrote:<br>
> .... This appears to have shown up from a DNS
upgrade.<br>
<br>
If one looks closely, one might happen to notice that<br>
SD is now front-ended by cloudflare.... (which uses<br>
DNS in a way that the really old firmware was vulnerable<br>
to).<br>
<br>
As I recall, SD had run into the bug some time ago<br>
(and was why newer firmware already existed to<br>
resolved it(*); it was even in the changelog for the<br>
early 2015 firmware releases)), but had widely rolled<br>
out their own load balancing and failover solutions<br>
which only returned one IP address. Cloudflare<br>
does things differently.<br>
<br>
btw, for the record, the latest firmware on SD's<br>
download pages is now 20161107 (with a suffix 'b'<br>
for the CableCARD firmware), but if you download<br>
it from the web site (as you stated) you will get the<br>
latest.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Nick here from Silicondust...<br>
<br>
</div>
<div class="gmail_extra">Confirming, we found and fixed a bug in
the firmware a few years ago relating to DNS handling.<br>
For HDHomeRun PRIME units it affects units running 20130117 or
older firmware.<br>
For HDHomeRun DUAL units it affects units running 20141124 or
older firmware.<br>
<br>
</div>
<div class="gmail_extra">The easiest fix is to unplug the WAN
port of your home router so the old HDHomeRun firmware is
happy, then upgrade it to the latest firmware (20161107b for
PRIME and 20161107 for DUAL).<br>
</div>
<div class="gmail_extra">The direct firmware download links can
be found on our website under Downloads, Linux.<br>
<br>
</div>
<div class="gmail_extra">We are beefing up our server
infrastructure... we now use CloudFlare for the first level.
Behind that we have caching servers in four locations for
speed, redundancy, and backend failover selection. Finally we
have the backend servers, with most services being served by
redundant servers. Linux and scripted builds all the way
through. I had fun setting that up :-)<br>
<br>
</div>
<div class="gmail_extra">Nick<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mythtv.org/mailman/listinfo/mythtv-users">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a>
<a class="moz-txt-link-freetext" href="http://wiki.mythtv.org/Mailing_List_etiquette">http://wiki.mythtv.org/Mailing_List_etiquette</a>
MythTV Forums: <a class="moz-txt-link-freetext" href="https://forum.mythtv.org">https://forum.mythtv.org</a>
</pre>
</blockquote>
I'm curious. Why would an HDHomeRun need to do DNS? I have three
HDHomeRun tuners connected to my backend on a dedicated network
which has no DNS service at all and they work just fine. The
backend connects to the HDHomeRun, not the other way around.<br>
Jay<br>
<br>
</body>
</html>