[Samba] FW: How to determine DNS anomaly

L. van Belle belle at samba.org
Fri May 6 14:48:27 UTC 2022














Your welkom, just, lets point this back to the list again, that way the thread keeps complete. 
















Yes, you need to sync the idmap. 







Don’t forget to stop samba when you do that. 







*( you probely allready did it).. 











Now, when everything is working, you have only one more change todo..







Change resolving again.. yeah, again.. 











look below for what to change, small change.  after the change   :  sudo netplan apply  







then wait 30 sec or so and run :







samba-tool dbcheck && samba-tool dbcheck --cross-nc







and run:







samba-tool drs showrepl to make sure its really done.. 
















DC1 







Network







network:







    version: 2







    renderer: networkd







    ethernets:







        eno1:







            addresses:







                - 192.168.50.11/24







            nameservers:







                  search [my.domain]







                addresses: [192.168.50.11, 10.0.1.9]







            routes:







                - to: default







                  via: 192.168.50.1

























DC2







Network







network:







    version: 2







    renderer: networkd







    ethernets:







        eno1:







            addresses:







                - 10.0.1.9/24







            nameservers:







                  search [my.domain]







                addresses: [10.0.1.9, 192.168.50.11]







            routes:







                - to: default







                  via: 192.168.50.1
































Van:
 Hakim Liso 


Verzonden:
 vrijdag 6 mei 2022 14:13


Aan:
 belle at samba.org


Onderwerp:
 AW: [Samba] FW: How to determine DNS anomaly

















Thanks for the quick Reply and Patience. i’ve followed your instructions and drs showrepl gives me the ggdc01 KCC again. This Looks really good.
 Sites recognized.
 But 
Rsync doesnt work anymore - rsync error: error starting client-server protocol (code 5) at main.c(1814) [Receiver=3.2.3] - i guess its because of the id mapping as mentioned in the wiki, which Needs to be synced. I will try to scp the /private db files and re-check. 
















You were both Right About the resolving, i didnt think as far as the entries Fixing itself after a proper Connection is established, i was stuck on the dns Manager trying to fix it. i still dont use loopback address tho and it Looks fine. Im good by now.
















Your help is really appreciated. 
















Keep up the good work. 
















Greetings



















Von: 



L. van Belle via samba



Gesendet: 
Freitag, 6. Mai 2022 12:27


An: 

samba at lists.samba.org



Betreff: 
[Samba] FW: How to determine DNS anomaly
















Aah... stupid email client and borking the html layout. 







a resend but in plain text. 
















Hai,
















Ah.. sorry direct mail and not the list.. 








Yes, thats one i missed, your : search MY.. I assumed.. (yeah that s wrong







assumptions..).. 
















but now I know you use netplan.. 







Add in the netplan config the following so you are always sure your







resolv.conf is right. 
















DC1 







Network







network:










 version: 2










 renderer: networkd










 ethernets:














 eno1:


















 addresses:






















 - 192.168.50.11/24


















 nameservers:






















 
 search [my.domain]






















 addresses: [192.168.50.11]


















 routes:






















 - to: default
























 via: 192.168.50.1

























and DC2. 







Network







network:










 version: 2










 renderer: networkd










 ethernets:














 eno1:


















 addresses:






















 - 10.0.1.9/24


















 nameservers:






















 
 search [my.domain]






















 addresses: [192.168.50.11]


















 routes:






















 - to: default
























 via: 192.168.50.1

























so, with that. 
















first do DC2. So you have 2 DC online again. 







change netplan 
config apply it, check resolv.conf and reboot. 







Then check again if replication is up again. 







If not report back. 

























on this : 







>>
 DC02 (Clients on this site will still use dc01 as NS / for gpos etc)
















if above works correctly, then do setup sysvol replication, windows  should 







go to the closed AD-DC.. 







But, first things first. 
















And why not upgrading you 21.10 to 22.04. 

























Greetz, 
















Louis











































-- 







To unsubscribe from this list go to the following URL and read the







instructions:
 
https://lists.samba.org/mailman/options/samba






















More information about the samba mailing list