Bug 7432 - Resolver only tries to resolve IPv4 address when looking for the DC
Summary: Resolver only tries to resolve IPv4 address when looking for the DC
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: Client Tools (show other bugs)
Version: unspecified
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-18 04:27 UTC by Kai Blin
Modified: 2011-06-28 15:14 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Blin 2010-05-18 04:27:38 UTC 
When trying to net ads join a current master s3 server to a win2k8r2 on an IPv6-only network, net tries to look up the domain controller. win2k8r2 replies to the DNS SRV query with the IPv6 address of the DC in the "additional data" field. net ignores that information and subsequently tries to look up the A record of the DC's hostname. On an IPv6-only network, this obviously fails.
Comment 1 Guenther Deschner 2010-05-18 09:50:25 UTC 
Oddly, this is nicely working on Fedora12 on RHEL6 beta.

Kai, you were seeing this on two Ubuntu versions, right ?
Comment 2 Kai Blin 2010-05-18 10:09:22 UTC 
I'm seeing that on Ubuntu 10.04 for sure, I'll have to look up the version of Ununtu the other VM is using once I get home. I'm certain that was pre-10.04, I'm just not sure if it's an 8.04 or 9.04.
Comment 3 Kai Blin 2011-06-28 15:14:57 UTC 
JRA and I tested this for 3.6.0 and it works, so I'm closing this.