julian.mehnle (Julian Mehnle)
- Login: julian.mehnle
- Email: [email protected]
- Registered on: 01/23/2010
- Last sign in: 03/08/2016
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 2 | 2 |
Activity
04/18/2013
-
07:44 AM Ruby Bug #8285: Resolv::DNS: TCP fallback fails with multiple resolvers
- Also, ruby -v actually is: ruby 1.9.3p374 (2013-01-15 revision 38858) [x86_64-darwin11]
-
07:42 AM Ruby Bug #8285: Resolv::DNS: TCP fallback fails with multiple resolvers
- Why has @monospace@ formatting been disabled in this Redmine? Bleh!
-
07:36 AM Ruby Bug #8285: Resolv::DNS: TCP fallback fails with multiple resolvers
- The problem is caused by my original TCP fallback code reusing a Resolv::DNS::Requester::TCP::Sender object that was initialized for one (the first) nameserver with a Resolv::DNS::Requester::TCP object that was initialized for another (t...
-
07:15 AM Ruby Bug #8285 (Closed): Resolv::DNS: TCP fallback fails with multiple resolvers
- Since my TCP fallback support patch from #3835 was merged Resolv::DNS would sometimes fail with a @"host/port don't match: <nameserver>:<port>"@ @Resolv::DNS::Requester::RequestError@ exception in @resolv.rb@, line 818 (Ruby 1.9.1). Thi...
10/30/2010
-
08:28 PM Ruby Feature #3835: Resolv::DNS: Retry via TCP on truncated UDP response
- =begin
Oh, thanks for reminding me! I recently discovered another issue with my patch. It fails if the system has more than one resolver configured in /etc/resolv.conf:
$ cat /etc/resolv.conf
# 192.168.0.123 does not exist,...
09/19/2010
-
05:51 AM Ruby Feature #3835: Resolv::DNS: Retry via TCP on truncated UDP response
- =begin
I've discovered a bug in my patch: Resolv::DNS::Message#tc returns a numerical value (0 or 1), not a boolean. Also, let's play it safe and #close the UDP requester before replacing it with the TCP requester.
I've successful...
09/16/2010
-
05:48 AM Ruby Feature #3835 (Closed): Resolv::DNS: Retry via TCP on truncated UDP response
- =begin
Resolv::DNS has code implementing DNS queries via TCP, but it is not currently used at all. Furthermore, any truncated responses received via UDP are parsed and intact RRs are used, silently discarding any truncated RRs. E.g.:
...