Short and easy test for you.
Assuming one of the non-working computers is named MYPC.
Go into dnsmgmt.msc and delete MYPC out of DNS.
Create a new A record for MYPC and point it wherever... 127.99.99.99 would
be fine.
Edit the record you just created, go to the security tab, click 'Add'
and
add MYPC to it. Set MYPC to have full control.
Go to MYPC and run 'ipconfig /registerdns'.
Refresh dnsmgmt.msc and see if the IP updated to the correct IP.
I'm betting that will fix it.
That can be for one of two reasons from what I've seen.
* The DNS record for MYPC was associated with the old MYPC AD account and
SID
* What appears to me to be a bug in Samba where you delete the old DNS
record that's associated with the wrong SID and the *new* MYPC still
can't
create a record--possible due to tombstoning as Rowland mentioned, but I
haven't tested it myself.
-A
On Thu, Nov 9, 2023 at 12:17?PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Thu, 9 Nov 2023 12:08:14 -0800
> "Aaron C. de Bruyn via samba" <samba at lists.samba.org>
wrote:
>
> > 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?
>
> From my reading of the initial post, the dns data wasn't deleted and if
> so, it will belong to the old computer and the new computer will not be
> able to update the dns records.
>
> Rowland
>
> >
> > 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
> > >
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>