Alpine Linux

the get_dns_domain_name() probably belongs to acf-alpine-baselayout hostname model.

require("dns")

function get_dns_domain_name()
        local f = io.popen("/bin/hostname -d")
        if f == nil then
                return nil
        end
        local n = f:read("*line")
        f:close()
        return n
end

function suggest_domain_controller(domain)
        if domain == nil then
                domain = get_dns_domain_name()
        end
        if domain == nil then
                return nil
        end
        local i,j
        local prio = nil
        local dc
        for i,j in pairs(dns.lookup("_ldap._tcp."..domain, "SRV")) do
                if prio == nil or j.srv.priority < prio then
                        dc = j.srv.target
                end
        end
        return dc
end

This is a feature request, not a bug. Join Domain is designed to test and join the domain specified in the config, not to join to an arbitrary domain.

I could not join the domain. Thats a bug. The web interface is supposed to generate/edit the config without users need to read the man pages, no?

Given the variety of settings that could influence domain joining, is it worth suggesting a domain in acf instead of letting user configure through smb.conf? krb would also need to get configured for this to work, certain places want computer put into specific OU on domain join, etc. Also, even with a config auto-generated through DNS, would the same config work with Server 2000, 2003 and 2008? Just a few thoughts to consider.

Wow, it's been a long time since I looked at this.

In response to ncopa: No, ACF is not supposed to generate the config. It is not a wizard. ACF is supposed to allow you to edit the config. After editing / creating the config, there needed to be a way for the ACF user to then use his config to join the domain. That's all the button is supposed to do.

It might or might not be possible to add the feature that you're asking for, but it was not part of the design. Right now, I don't have plans to add this feature.

Ted: as mentioned in my last post, given the diversity of domains that could be joined, I don't think it's worth trying to generate a sensible config to join a given domain (after all, with most Windows domains, there's one DNS domain that corresponds to one AD domain, but with larger organizations, there'd most likely be multiple AD domains, and there's no way that you could just guess...). It's simple enough to find a config online that can then be used on the Expert tab in ACF.