samba - Aug 2020 - Changing IP Scope on a Samba DC

Thank you for your help Rowland.

I have done as Andrew suggested with mixed success. The biggest problem
I've found is that the internal DNS is seriously screwy. There are no zone
files for the domain that I can find and no server suggests it's the master
- yet when dc1 falls over they all fall down. I'm going to find somewhere
else to seek assistance with that because it's a bind issue not a Samba
issue, but the 192.168.0.0/22 idea has worked to some degree, so thank you
both for that!

On Sat, Aug 29, 2020 at 12:50 AM Rowland penny via samba <
samba at lists.samba.org> wrote:
> On 29/08/2020 07:54, Peter Pollock via samba wrote:
> > Andrew, I very much appreciate your swift reply and your expertise. I
> > readily admit I'm a little out of my depth here. I'm sitting
here in
> > California at almost midnight with just the weekend to get done all I
> need
> > to do on the network and I fear this may be derailing my plans.
> >
> > This article on the Samba Wiki
> >
> https://wiki.samba.org/index.php/Changing_the_IP_Address_of_a_Samba_AD_DC
> seems
> > to suggest I need to demote and repromote if I change the address, is
> that
> > also the same if I change the subnet?
> No, the DC's ipaddress points to the DC, so if you change either, it is
> easier to demote and re-join rather than trying to change every instance
> of the IP or name. You probably could change either, but, because they
> are in numerous places, it is fraught with danger, you might miss some.
> >
> > I'm sorry if that's a dumb question, but I'm having severe
problems with
> > these servers and I really don't want to screw anything up because
I try
> > something stupid.
>
> You probably have a reverse zone called '2.168.192.in-addr.arpa'
(If
> unsure 'samba-tool dns zonelist <dc_name> -P' will confirm
this). If you
> follow Andrew's suggestion (and I urge you to do so), you will need to
> replace it with '168.192.in-addr.arpa'
>
> Once this is done and you have recreated any fixed IP machines records,
> dhcp should then recreate the other records for you.
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On 29/08/2020 22:33, Peter Pollock wrote:
> Thank you for your help Rowland.
>
> I have done as Andrew suggested with mixed success. The biggest 
> problem I've found is that the internal DNS is seriously screwy. There 
> are no zone files for the domain that I can find and no server 
> suggests it's the master - yet when dc1 falls over they all fall down. 
> I'm going to find somewhere else to seek assistance?with that because 
> it's a bind issue not a Samba issue, but the 192.168.0.0/22 
> <http://192.168.0.0/22> idea has worked to some degree, so thank you 
> both for that!
I wonder if you are using flatfiles ? You shouldn't be. Can you post 
your bind (named) conf files .

Rowland

On 31/08/2020 00:12, Peter Pollock wrote:
> This is moving somewhat away from Samba, I'm sorry.
>
No it isn't, I think I may have spotted a problem with your bind9 files, 
If you can tell me what IP range you use, I will give you a set of files 
to try.

I think it is 192.168.2.0/24 and if it is, you have your reverse zone in 
a flat file and presumably in AD as well.

Rowland