@techreport{ietf-krb-wg-krb-dns-locate-03,
    number =    {draft-ietf-krb-wg-krb-dns-locate-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-krb-wg-krb-dns-locate/03/},
    author =    {Ken Hornstein and Jeffrey E. Altman},
    title =     {{Distributing Kerberos KDC and Realm Information with DNS}},
    pagetotal = 7,
    year =      2002,
    month =     jul,
    day =       29,
    abstract =  {Neither the Kerberos V5 protocol {[}RFC1510{]} nor the Kerberos V4 proto- col {[}RFC????{]} describe any mechanism for clients to learn critical configuration information necessary for proper operation of the pro- tocol. Such information includes the location of Kerberos key dis- tribution centers or a mapping between DNS domains and Kerberos realms. Current Kerberos implementations generally store such configuration information in a file on each client machine. Experience has shown this method of storing configuration information presents problems with out-of-date information and scaling problems, especially when using cross-realm authentication. This memo describes a method for using the Domain Name System {[}RFC1035{]} for storing such configuration information. Specifically, methods for storing KDC location and hostname/domain name to realm mapping information are discussed.},
}