From: "Torsten Bögershausen" <tboegi@web.de>
To: Jonathan Nieder <jrnieder@gmail.com>,
"Kyle J. McKay" <mackyle@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: git_inetd_server: run git-http-backend using inetd
Date: Sat, 19 Jul 2014 08:21:13 +0200 [thread overview]
Message-ID: <53CA0E59.5030103@web.de> (raw)
In-Reply-To: <20140717221056.GO12427@google.com>
On 07/18/2014 12:10 AM, Jonathan Nieder wrote:
> Hi,
>
> Kyle J. McKay wrote:
>
>> When I then try to fetch using a "git://host/..." URL where "host"
>> is an mDNS host name, the 0010 patch causes git to attempt to lookup
>> a DNS SRV record on the non-mDNS regular DNS service (a violation of
>> RFC 6762 [4] section 22) and this is what has to time out before the
>> real fetch can start.
> That patch uses res_query from libresolv to do the lookup. It doesn't
> know what DNS server to use and relies on system libraries to get it
> right.
>
> It was added to respond to a feature request within Debian but it is
> intended to eventually go upstream. I'm glad you found this issue
> before that could happen. :)
>
> Should git automatically disable the SRV lookups when it sees one of
> the six domains named in RFC6762, or is there some system library call
> that can use mDNS when appropriate automatically (or get partway there
> without having to hard-code the domains)?
>
> Thanks,
> Jonathan
(My apologies, if this is spamish), but just to verify what is going on:
git fetch git://host.local/...
results in a DNS lookup ?
Kyle, did you verify the lookup with wireshark or a similar tool?
Jonathan, (I'm good in searching, but bad in finding)
could you point out where the source code for the git package for
debian is ?
I recently learned about mDNS, and will probably do some tests
and experiments later, and would like to test the lookup feature
of "0010".
Thanks.
/Torsten
next prev parent reply other threads:[~2014-07-19 6:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:28 git_inetd_server: run git-http-backend using inetd Kyle J. McKay
2014-07-17 22:10 ` Jonathan Nieder
2014-07-17 23:38 ` Kyle J. McKay
2014-07-18 2:22 ` Jonathan Nieder
2014-07-18 6:48 ` Kyle J. McKay
2014-07-18 17:16 ` Jonathan Nieder
2014-07-19 0:08 ` Kyle J. McKay
2014-07-19 0:19 ` Jonathan Nieder
2014-07-19 1:54 ` Kyle J. McKay
2014-07-19 6:21 ` Torsten Bögershausen [this message]
2014-07-19 17:06 ` Jonathan Nieder
2014-07-20 6:10 ` Torsten Bögershausen
2014-07-20 15:25 ` Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CA0E59.5030103@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mackyle@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).