samba - Nov 2023 - DNS updates, machine name changes...

We have a situation where AD's dns isn't right. It's a result of us
moving/renaming machines, so I'm sure it's a self-induced problem.
But I'm not sure the "right" way to go about fixing it.

So, here's how we "caused" it. Hopefully someone can tell me how
to best
fix it.

Lets assume two machines.
Machine 1: BuildingA-Sales1.ad.somedomain.net
Machine 2: BuildingB-Finance2.ad.somedomain.net

Now assume the two machines/users swap places. And they take their machines
with them.
So now, machine 1: is BuildingB-Finance2.ad.somedomain.net
...and vice versa.

We did remove the machines from the domain and re-join them.
And while removed, we went and removed the machine accounts using the
Windows Computers/Users tool.
Then we re-joined the machines to the domain.

But the IP's they resolve to are reversed.
For example; Machine 1 is till resolving to the IP it would get in Building
A, (different IP netblock) instead of the block it's actually getting in
Building B. (i.e. dig  BuildingB-Finance2.ad.somedomain.net returns the IP
"Machine 1" is getting in Building A.)

I think I've seen this get discussed recently, and if someone can point me
at that discussion instead of typing a new reply, (or at a wiki article)
that would be fab.

So, how do I do this "right"?

TIA
-Greg

You might be running into what I just ran into and posted about a day or so
ago.

When did you delete the names out of DNS?

If it was *after* you re-joined them to the domain, Samba appears to not
allow the records to be created.

If you manually create records for those names and grant the computer
account full control on the record, Samba appears to allow updates again.

If you deleted the names out of DNS *before* you re-joined them to the
domain, it's probably not the issue I ran into.


On Thu, Nov 9, 2023 at 10:09?AM Greg Sloop <gregs--- via samba <
samba at lists.samba.org> wrote:
> We have a situation where AD's dns isn't right. It's a result
of us
> moving/renaming machines, so I'm sure it's a self-induced problem.
> But I'm not sure the "right" way to go about fixing it.
>
> So, here's how we "caused" it. Hopefully someone can tell me
how to best
> fix it.
>
> Lets assume two machines.
> Machine 1: BuildingA-Sales1.ad.somedomain.net
> Machine 2: BuildingB-Finance2.ad.somedomain.net
>
> Now assume the two machines/users swap places. And they take their machines
> with them.
> So now, machine 1: is BuildingB-Finance2.ad.somedomain.net
> ...and vice versa.
>
> We did remove the machines from the domain and re-join them.
> And while removed, we went and removed the machine accounts using the
> Windows Computers/Users tool.
> Then we re-joined the machines to the domain.
>
> But the IP's they resolve to are reversed.
> For example; Machine 1 is till resolving to the IP it would get in Building
> A, (different IP netblock) instead of the block it's actually getting
in
> Building B. (i.e. dig  BuildingB-Finance2.ad.somedomain.net returns the IP
> "Machine 1" is getting in Building A.)
>
> I think I've seen this get discussed recently, and if someone can point
me
> at that discussion instead of typing a new reply, (or at a wiki article)
> that would be fab.
>
> So, how do I do this "right"?
>
> TIA
> -Greg
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>