Paul Littlefield
2023-Sep-25 15:18 UTC
[Samba] new DC preparation, nslookup and dig errors
On 25/09/2023 15:17, Rowland Penny via samba wrote:> If you haven't joined as a DC, then at that point, there will not be > such a record for the new DC, it gets created when you first start your > new DC.OK, I was more concerned about the actual 'network error' as shown in my original post... "communications error to 130.130.0.219#53: timed out" ... I have tried a few different times and get the same error each time. This error is NOT shown when I test on the other running DCs. This is what I worried about and need advice on whether to risk a join or not?! Could it be to do with the different IP address range? Details for you:- 'DC3' = Ubuntu 18.04.6 LTS, Samba Version 4.7.6-Ubuntu, 130.130.0.218/16 'DC4' = Ubuntu 18.04.6 LTS, Samba Version 4.7.6-Ubuntu, 130.130.0.218/16 'DC5' = Ubuntu 22.04.3 LTS, Samba Version 4.15.13-Ubuntu, 130.130.251.5/16 Thanks, -- Paul Littlefield
On Mon, 25 Sep 2023 15:18:01 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote:> On 25/09/2023 15:17, Rowland Penny via samba wrote: > > If you haven't joined as a DC, then at that point, there will not be > > such a record for the new DC, it gets created when you first start > > your new DC. > > > OK, I was more concerned about the actual 'network error' as shown in > my original post... > > > "communications error to 130.130.0.219#53: timed out" > > > ... I have tried a few different times and get the same error each > time. This error is NOT shown when I test on the other running DCs. > This is what I worried about and need advice on whether to risk a > join or not?! Could it be to do with the different IP address range?Whilst anything is possible, if you are trying to connect to the internal dns server on a machine that isn't yet a DC, then it will time out, because there isn't a dns server there yet. Of course. I may be misunderstanding things here. Rowland