Bug#526823: getaddrinfo still fails

2009-05-12 Thread Andrew Pimlott 
On Tue, May 12, 2009 at 01:31:40AM +0200, Aurelien Jarno wrote:
 On Mon, May 11, 2009 at 11:53:17AM -0700, Andrew Pimlott wrote:
  This problem is back for me as well, after being fixed in 2.9-6.  2.9-7
  works, 2.9-10 fails.  options single-request in my resolv.conf does
  nothing.  (Could you verify that is the correct syntax?)  Here is my DNS
  trace with single-request set.
  
 
 Yes, this option is the correct one. Note that this has improved in
 version 2.9-12. You should try this version.

That test was under 2.9-12.  Sorry for not mentioning.

Andrew



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526823: getaddrinfo still fails

2009-05-11 Thread Andrew Pimlott 
This problem is back for me as well, after being fixed in 2.9-6.  2.9-7
works, 2.9-10 fails.  options single-request in my resolv.conf does
nothing.  (Could you verify that is the correct syntax?)  Here is my DNS
trace with single-request set.

11:51:45.491726 IP (tos 0x0, ttl 64, id 26230, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.43124  192.168.0.1.53: [udp sum ok] 39751+ A? google.com. 
(28)
11:51:45.497307 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 72)
192.168.0.1.53  192.168.0.101.43124: [udp sum ok] 39751- q: A? google.com. 
1/0/0 google.com. A 74.125.67.100 (44)
11:51:45.497435 IP (tos 0x0, ttl 64, id 26231, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.43124  192.168.0.1.53: [udp sum ok] 48239+ ? google.com. 
(28)
11:51:45.521547 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.1.53  192.168.0.101.43124: [udp sum ok] 48239- q: ? 
google.com. 0/0/0 (28)
11:51:45.522358 IP (tos 0x0, ttl 64, id 26237, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.56385  192.168.0.1.53: [udp sum ok] 39751+ A? google.com. 
(28)
11:51:45.525636 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 72)
192.168.0.1.53  192.168.0.101.56385: [udp sum ok] 39751- q: A? google.com. 
1/0/0 google.com. A 74.125.67.100 (44)
11:51:45.525705 IP (tos 0x0, ttl 64, id 26238, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.56385  192.168.0.1.53: [udp sum ok] 48239+ ? google.com. 
(28)
11:51:45.550947 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.1.53  192.168.0.101.56385: [udp sum ok] 48239- q: ? 
google.com. 0/0/0 (28)
11:51:45.551705 IP (tos 0x0, ttl 64, id 26245, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.57011  192.168.0.1.53: [udp sum ok] 37693+ A? google.com. 
(28)
11:51:45.555200 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 72)
192.168.0.1.53  192.168.0.101.57011: [udp sum ok] 37693- q: A? google.com. 
1/0/0 google.com. A 74.125.67.100 (44)
11:51:45.555263 IP (tos 0x0, ttl 64, id 26246, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.57011  192.168.0.1.53: [udp sum ok] 14101+ ? google.com. 
(28)
11:51:45.578284 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.1.53  192.168.0.101.57011: [udp sum ok] 14101- q: ? 
google.com. 0/0/0 (28)
11:51:45.578958 IP (tos 0x0, ttl 64, id 26251, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.43912  192.168.0.1.53: [udp sum ok] 37693+ A? google.com. 
(28)
11:51:45.582282 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 72)
192.168.0.1.53  192.168.0.101.43912: [udp sum ok] 37693- q: A? google.com. 
1/0/0 google.com. A 74.125.67.100 (44)
11:51:45.582343 IP (tos 0x0, ttl 64, id 26252, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.101.43912  192.168.0.1.53: [udp sum ok] 14101+ ? google.com. 
(28)
11:51:45.610221 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP 
(17), length 56)
192.168.0.1.53  192.168.0.101.43912: [udp sum ok] 14101- q: ? 
google.com. 0/0/0 (28)

Andrew



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526823: getaddrinfo still fails

2009-05-11 Thread Aurelien Jarno 
On Mon, May 11, 2009 at 11:53:17AM -0700, Andrew Pimlott wrote:
 This problem is back for me as well, after being fixed in 2.9-6.  2.9-7
 works, 2.9-10 fails.  options single-request in my resolv.conf does
 nothing.  (Could you verify that is the correct syntax?)  Here is my DNS
 trace with single-request set.
 

Yes, this option is the correct one. Note that this has improved in
version 2.9-12. You should try this version.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org