search for: dislectics

Displaying 9 results from an estimated 9 matches for "dislectics".

Did you mean: dislectic
2020 Feb 12
0
Failover DC did not work when Main DC failed
> > Hello Louis, > > Thanks for your reply. > > For that dig command I get... > > > root at dc3.mydomain.com ~ $ (screen) dig NS $(hostname -d) > > ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS mydomain.com > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63144 > ;;
2020 Feb 12
4
Failover DC did not work when Main DC failed
What do you see/get when you run: dig NS $(hostname -d) With 2 dc's you should see 2 records. In the past this was a bug at samba joins so only 1 NS record existed. Worth to have a look at. And adding this to /etc/resolv.conf: options timeout:2 options attempts:3 options rotate Also might help. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba
2020 Apr 30
3
bind9 refuses to start -> zone has no NS records
Hi Denis, thanks a lot! > you said that the zone is empty. It is not a problem per se but for some > time Bind-DLZ has been a bit more strict and ask for a NS record for > every zone. So you just have to create a NS field in your zone pointing > to one of your DC and you should be fine. Internal DNS does not have > this requirements. > > samba-tool dns mydc
2020 Feb 12
2
Failover DC did not work when Main DC failed
On 12/02/2020 12:54, L.P.H. van Belle via samba wrote: > > >> Hello Louis, >> >> Thanks for your reply. >> >> For that dig command I get... >> >> >> root at dc3.mydomain.com ~ $ (screen) dig NS $(hostname -d) >> >> ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS mydomain.com >> ;; global options: +cmd
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 13:37 schrieb L.P.H. van Belle via samba: > So if i understand correctly. > You removed : /var/lib/samba/private/dns_update_cache > > Stopped samba and started samba and you got the dns A for hostname DC back > in /var/lib/samba/private/dns_update_cache ?? Yes! repeated that once more now. Same result. > Hmm.. >> SOA contains
2018 May 09
0
Samba4 on Ubuntu 18.04 Howto setup ADDC with bind9_DLZ
I was rereading this i missing one thing, my dislectic got me again.. In the last part. Just before all systemctl's. This : and we change the systemd-resolved and point it to the IP ( NOT localhost ) of the server now change the systemd-resolvd DNS. sed "s/DNS=8.8.8.8/DNS=$(hostname -i)/g" /etc/systemd/resolved.conf The sed line should be : sed -i
2018 May 09
0
Samba4 on Ubuntu 18.04 Howto setup ADDC with bind9_DLZ (extra part 4.8.1 samba)
Hai, I detected a minor error and i added a quick fix. And i'm testing my 4.8.1 debian package on ubuntu 18.04, see below.. Syslog shows. May 9 14:50:26 ubuntu1804 systemd[9448]: /lib/systemd/system-generators/netplan failed with exit status 1. The fix is: editor /etc/netplan/01-netcfg.yaml The last adresses: needs a server adres. cat /etc/netplan/01-netcfg.yaml # This file describes
2018 May 09
2
Samba4 on Ubuntu 18.04 Howto setup ADDC with bind9_DLZ
Hai, @Rowland. Yes yes, you did say you hate systemd. :-) I had a hard(er)time on this one also but i got passed it. ;-) But you and everybody else on the list, please review this setup. And a very big thank you Rowland for the start of it. This should be a good base to start with as howto for ubuntu 18.04 systemd based. Any suggestion additions please add them, below is also the order
2019 Aug 05
6
samba dlz. bind9 nslookup is wrong
... From your output below.. >> Uncomment only single database line, depending on your BIND version << Then tell uss, why are 3 lines uncommented? I suggest, run : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize it where needed, and show me your server setup. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: