<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Alexey Zakhlestin's blog - Latest Comments in DNS SRV-records support in HTTP-browsers</title><link>http://alexeyzakhlestinsblog.disqus.com/</link><description></description><atom:link href="https://alexeyzakhlestinsblog.disqus.com/dns_srv_records_support_in_http_browsers/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 04 Jan 2021 06:25:43 -0000</lastBuildDate><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-5211803092</link><description>&lt;p&gt;Let's do it 22, maybe after my death they will implement this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sergey Sergeev</dc:creator><pubDate>Mon, 04 Jan 2021 06:25:43 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-4558661968</link><description>&lt;p&gt;They didn't.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RelatedTitle</dc:creator><pubDate>Mon, 29 Jul 2019 23:10:38 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-4269263737</link><description>&lt;p&gt;Hi i want a  sexy  girlfriend&amp;lt;&lt;b&gt;spoiler&amp;gt;&lt;/b&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Noman</dc:creator><pubDate>Fri, 04 Jan 2019 09:53:36 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-4269261823</link><description>&lt;p&gt;Hii&lt;br&gt;Helo&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Noman</dc:creator><pubDate>Fri, 04 Jan 2019 09:52:22 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3584642908</link><description>&lt;p&gt;still hoping for it!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Filippos Vasilakis</dc:creator><pubDate>Wed, 25 Oct 2017 16:49:39 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3262712614</link><description>&lt;p&gt;Yes... you can use an IP address, but in the context of SRV records (where you're trying to even further abstract the actual IP by use of FQDN's pointing to address:port, rather than just address)... it seems like an odd requirement. If you e.g. 'always' know the IP, you don't need SRV records, except to make the URI for the resource look 'pretty' (i.e. to abstract the Port, not to load balance). I'd ALWAYS have a target pointing to an 'A' record... sometimes a CNAME... but A records are safer if you do - or might - ever use certificates for the resource concerned (CN must match FQDN). Of course we use very low TTL's for records for load balanced systems. The trailing dot is a BIND thing... your DNS and, more particularly, its UI may or may not require it... most are automatic these days.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Sadler</dc:creator><pubDate>Wed, 19 Apr 2017 02:42:31 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3262706229</link><description>&lt;p&gt;Ummmm.... wrong. SIP is w-a-y more time sensitive than... well, pretty much everything and SRV is almost mandatory for it. So, browser publishers don't support it because they are slack, or it needs refinement or whatever... not because SRV isn't the 'right' protocol to offer multi-address, multi-port load sharing without the expense of e.g L7 switches. An 'RFC' is exactly that, so you comment or you support. Doing nothing sucks. Sorry.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Sadler</dc:creator><pubDate>Wed, 19 Apr 2017 02:32:44 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3154030706</link><description>&lt;p&gt;The reason this is not supported is that it can't serve the purpose you purport.&lt;/p&gt;&lt;p&gt;It works for SMTP because delays of a few minutes are not an issue. But for a timing sensitive application such as browsing, what good would this do?&lt;/p&gt;&lt;p&gt;In your example, the browser might first select &lt;a href="http://www1.example.com" rel="nofollow noopener" target="_blank" title="www1.example.com"&gt;www1.example.com&lt;/a&gt;. If that didn't respond in 21 seconds, the browser would then go for &lt;a href="http://www2.example.com" rel="nofollow noopener" target="_blank" title="www2.example.com"&gt;www2.example.com&lt;/a&gt;. If that didn't respond at the 42 second mark, the browser would go for &lt;a href="http://www-backup.example.com" rel="nofollow noopener" target="_blank" title="www-backup.example.com"&gt;www-backup.example.com&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Who exactly is going to wait 42 seconds for a page to load?&lt;/p&gt;&lt;p&gt;The load balancing you get with multiple A records is the best you can do for applications that require responsiveness. You can't provide responsive fault tolerance using just DNS.&lt;/p&gt;&lt;p&gt;And then, what exactly should the browser consider a failure that requires a fallback? What if the TCP connection can be established, but there's no HTTP response? What if there's an HTTP response, but it's an error?&lt;/p&gt;&lt;p&gt;This is not a bug in Mozilla. This is the absence of a feature; in this case, a braindead misfeature that ought not to be proposed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Elo</dc:creator><pubDate>Tue, 14 Feb 2017 02:30:12 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3040285560</link><description>&lt;p&gt;Can I use IP address in the TARGET part of a SRV record ? Who adds the &lt;br&gt;trailing dot to make the hostename absolute ? is it the DNS server or &lt;br&gt;the client ?&lt;/p&gt;&lt;p&gt;&lt;a href="http://stackoverflow.com/questions/41003722/can-i-use-an-ip-address-in-a-srv-record" rel="nofollow noopener" target="_blank" title="http://stackoverflow.com/questions/41003722/can-i-use-an-ip-address-in-a-srv-record"&gt;http://stackoverflow.com/qu...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shmulik Klein</dc:creator><pubDate>Wed, 07 Dec 2016 07:19:16 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-3040135949</link><description>&lt;p&gt;Can I use IP address in the TARGET part of a SRV record ? Who adds the trailing dot to make the hostename absolute ? is it the DNS server or the client ?&lt;/p&gt;&lt;p&gt;&lt;a href="http://stackoverflow.com/questions/41003722/can-i-use-an-ip-address-in-a-srv-record" rel="nofollow noopener" target="_blank" title="http://stackoverflow.com/questions/41003722/can-i-use-an-ip-address-in-a-srv-record"&gt;http://stackoverflow.com/qu...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shmulik Klein</dc:creator><pubDate>Wed, 07 Dec 2016 04:19:15 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-2982419630</link><description>&lt;p&gt;Make that 15 years.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">network101</dc:creator><pubDate>Thu, 03 Nov 2016 03:14:32 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-2808127314</link><description>&lt;p&gt;Hope they will fix it before 20 years anniversary.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yura</dc:creator><pubDate>Thu, 28 Jul 2016 09:17:04 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-1529754860</link><description>&lt;p&gt;it is 2014 now, seem like FF still not not srv&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jing</dc:creator><pubDate>Wed, 06 Aug 2014 03:54:36 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-276832367</link><description>&lt;p&gt;But it is not committed and waits for approval. I doubt, that is the longest-living bug in mozilla, but, still, 10 years is a great age for a bug. Let’s party! &lt;br&gt;_______________&lt;br&gt;Steven&lt;br&gt;&lt;a href="“http://dnslookup.org.uk”" rel="nofollow noopener" target="_blank" title="“http://dnslookup.org.uk”"&gt; DNS Look up&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">brain Steven</dc:creator><pubDate>Thu, 04 Aug 2011 03:10:52 -0000</pubDate></item><item><title>Re: DNS SRV-records support in HTTP-browsers</title><link>http://blog.milkfarmsoft.com/2009/09/dns-srv-records-support-in-http-browsers/#comment-80290038</link><description>&lt;p&gt;It is a weak substitute, but in my experience recent browsers will handle multiple A records for the same domain name sensibly. That is, if you have 2 A records for the same name, the browser will pick one, and if it times out, switch to the other. Since the DNS hands out the addresses in random order, this provides crude load balancing and failover. Not nearly as good as supporting SRV, but something nonetheless.&lt;/p&gt;&lt;p&gt;Daniel Feenberg&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Feenberg</dc:creator><pubDate>Thu, 23 Sep 2010 09:15:01 -0000</pubDate></item></channel></rss>