samba - Mar 2004 - Samba 3, winbind, win2k AD: Kerberos question

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks, after a little head banging, I got winbind chatting with the
domain control ( win2k server ) by hard coding my realm info into
krb5.conf.

My question is this:  Is there a cleaner, more fault tolerant method
than this?  I googled, and read about dns srv records being used (
intead of hardcoding ), which I understand win2k uses to begin with,
but I don't know how to turn those on on my linux box.

Can anybody point me in the right direction?  I'd apprecaite it.

- --
Sean Kennedy
PGP public key: http://tpno.org/keys/0xFC1C377F.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAYwnsIjyA6vwcN38RAhx+AJ4y37cu3hYsHljijcMYRl3owhvaOACbBnal
7Eu52tCX1rv4H7ytxofi+7c=+L+l
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sean Kennedy wrote:

| My question is this:  Is there a cleaner, more
| fault tolerant method than this?  I googled, and read about
| dns srv records being used ( intead of hardcoding ), which I
| understand win2k uses to begin with, but I don't know how to
| turn those on on my linux box.

If you are using MIT, then you will need to enable
- -DKRB5_DNS_LOOKUP -DKRB5_DNS_LOOKUP_KDC at compile time
(RH doesn't do this IIRC) and then use the following

## /etc/krb5.conf
[libdefaults]
~        dns_fallback = true




- --
cheers, jerry
- ----------------------------------------------------------------------
Hewlett-Packard            ------------------------- http://www.hp.com
SAMBA Team                 ---------------------- http://www.samba.org
GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
"If we're adding to the noise, turn off this song" --Switchfoot
(2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAYyJfIR7qMdg1EfYRAhpFAJ4z4FLKEmWjiL3gvJH5pdoX5aWlLwCfWzXr
9KPNaHnO7Q9qkM4J0qKcBBU=NPQh
-----END PGP SIGNATURE-----