search for: vagrent

Displaying 4 results from an estimated 4 matches for "vagrent".

Did you mean: vagrant
2023 Jan 16
1
Debian11 Samba backport and bind9
As I said, both DC are installed via Vagrent, starting the setup with 9.18 I have the problem, starting with 9.16 everything is running. The configuration is always the same. Am 16.01.23 um 21:36 schrieb Rowland Penny via samba: > > > On 16/01/2023 19:55, Ingo Asche via samba wrote: >> Ah, ok, just saw it. Sorry, I missed...
2023 Jan 16
1
Debian11 Samba backport and bind9
On 16/01/2023 20:52, Stefan Kania via samba wrote: > As I said, both DC are installed via Vagrent, starting the setup with > 9.18 I have the problem, starting with 9.16 everything is running. The > configuration is always the same. > > I am getting confused now (not that it takes much) Are you saying that none of your 4.17.x DC's work with Bind 9.18 ? Ingo seems to be sayi...
2023 Jan 16
1
Debian11 Samba backport and bind9
...#39;s exactly what I'm saying. I can add output from all three DC's if necessary. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um 22:02: > > > On 16/01/2023 20:52, Stefan Kania via samba wrote: >> As I said, both DC are installed via Vagrent, starting the setup with >> 9.18 I have the problem, starting with 9.16 everything is running. >> The configuration is always the same. >> >> > > I am getting confused now (not that it takes much) > > Are you saying that none of your 4.17.x DC's work with B...
2023 Jan 16
1
Debian11 Samba backport and bind9
On 16/01/2023 19:55, Ingo Asche via samba wrote: > Ah, ok, just saw it. Sorry, I missed that. > > I can only add then, all three DC's in my little net are installed with > bind 9.18 and working all the same without errors. That would tend to dispel my worries, so it is possible that it is some misconfiguration on Stefan's machine. I know I once joined a DC and forgot the