When I was testing my roll out of SGD, as I'm sure this must be common
in many environments.. The IP is different internally, from what you
access externally. I decided to install the OS with the external FQDN as
the hostname, then make the internal DNS resolve it to the internal IP..
(So they can at least manage it internally.) Seemed like a good plan..
Everything seemed fine at first, but setting it up this way broke my AD
authentication. I can see on the network when I user tries to login, the
host tries to resolve _nfsv4idmapdomain.<EXTERNAL_DOMAIN>, and obviously
fails, then it tries to resolve _nfsv4idmapdomain twice.
It seems like it's ignoring what I setup through the ArrayManager, and
using the OS DNS configuration to decide what is the AD domain.
I've tried putting the internal domain into the domain search in
resolv.conf, hoping when it resolved the '_nfsv4idmapdomain', with no
attached domain, it would resolve the proper entry.
I'm fairly sure my AD auth setup is correct. Got the AD component going
just fine a few times (after a few headaches), but now it's actually
really simple to get going.
Anyone have any ideas?
- Trev
_______________________________________________
SGD-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sgd-users
