Displaying 4 results from an estimated 4 matches for "rfc2782".
2019 Mar 09
2
Auto MX Email Client configuration, the right way?
...MUA will need to prompt the user to enter
the FQDN and port information directly, or use some other heuristic.
In the case of multiple SRV records returned for a particular
service, the MUA MUST use the priority and weight fields in the
record to determine which one to use (as per [RFC2782]).
[..]
again:
[..]
When a user identifier is required, MUAs MUST first
use the full email address provided by the user, and if that results
in an authentication failure, SHOULD fall back to using the "local-
part" extracted from the email address. This is in line w...
2016 Aug 25
0
missing dns records? _ldaps._tcp ?
...for "example.com", this
would result in an SRV-specific domain name of
"_ldap._tcp.example.com".
c. Issue a DNS query for the SRV resource records associated
with the domain name formed in step 7.4.5.b.
https://tools.ietf.org/html/rfc2782
no word about ssl/tls.. arg :-/
So, its all optional, as im seeing here.
So if you preffer SSL over STARTTLS then its an option to add
the SRV records or is an application uses/prefferes it.
Of default _ldap._tcp with the ldaps port and set higher preference on the SRV record.
One i must...
2009 Oct 14
0
getaddrinfo() and SRV records
Ssh calls getaddrinfo() to get the server address when it makes a
connection, but ignores the port, which I think is bad. Instead it calls
getservbyname(), which is redundant, as getaddrinfo() normally does that for
you.
Among other things, this makes it impossible to use SRV records (rfc2782) on
the server end to point the client at a different port.
Yes, I know that getaddrinfo() does not use SRV records in the default linux
implementation. But that's no reason to ignore the port.
I have attached a patch for your consideration. I am not advocating that
this be committed as-is,...
2016 Aug 25
6
missing dns records? _ldaps._tcp ?
Ok thank you guys for you input.
So we need tot add something here :
cat /var/lib/samba/private/dns_update_list | grep ldap
${IF_RWDC}SRV _ldap._tcp.${DNSDOMAIN} ${HOSTNAME} 389
${IF_RWDC}SRV _ldap._tcp.dc._msdcs.${DNSDOMAIN} ${HOSTNAME} 389
${IF_RWDC}SRV _ldap._tcp.${DOMAINGUID}.domains._msdcs.${DNSFOREST}