SAMBA again

[David Bandel]

On 11/24/05, Roger Oberholtzer <roger at opq.se> wrote:
[snip]
>
> The whole name system here is odd. They use a NAT. Machines that are
> externally available are not available internally by their externally
> known address. This means that they have a local DNS that tells where
> these machines are. So, I manage my own DNS for the opq.se domain, which
> is these days behind their NAT. (We were bought out a bit back.)
> Externally, the opq.se DNS works as expected. Internally, I have to tell
> the IT guy what addresses are in my DNS so he can add them to the local
> name system using their internal addresses. I would have thought that
> the NAT would have handled this directly. But, that is not how it is
> done.

This is what split horizon DNS is for. BIND 9 has supported this for a
long time now. Manually maintaining /etc/hosts files is too much
trouble.

>
> One additional question: I have asked the IT guy here for a 'machine
> account' in the active directory. He is looking in to it. The SAMBA docs
> are a bit sketchy on this, but is the very act of the admin logging in
> from my machine what it takes to create the machine account? The docs
> mention many steps, but I think the assume that I know the relationship
> between them. When it come to the MS part, this is a bad assumption.

The machine account is created by the machine and if its part of an NT
domain, should be added to that domain automagically when it enters
the domain.

Ciao,

David A. Bandel
--
Focus on the dream, not the competition.
            - Nemesis Air Racing Team motto