similar to: Samba4 Secondary DC Replication Concerns

On Thu, 31 May 2018 09:42:50 +0000 Paul Littlefield via samba <samba at lists.samba.org> wrote: > On 29/05/18 12:55, Paul Littlefield via samba wrote: > > Hello List, > > > > I have successfully migrated my DCs to 4.7.6-Ubuntu > > > > However, I still have some traces of the old DCs in the DNS... > > > > $ samba-tool dns query dc3 mydomain.com

Hello List, I have successfully migrated my DCs to 4.7.6-Ubuntu However, I still have some traces of the old DCs in the DNS... $ samba-tool dns query dc3 mydomain.com @ ALL Name=, Records=8, Children=0 SOA: serial=570, refresh=900, retry=600, expire=86400, minttl=0, ns=dc3.mydomain.com. NS: samba.mydomain.com. (flags=600000f0, serial=110, ttl=900) NS: dc3.mydomain.com.

On 02/03/2020 11:51, Paul Littlefield via samba wrote: > On 02/03/2020 10:49, Rowland penny via samba wrote: >> Does your DC have a fixed IP and if not, why not ? > > Yes, using netplan in Ubuntu 18.04... > > network: > ? ethernets: > ??? ens18: > ????? addresses: > ????? - 130.130.0.218/16 > ????? gateway4: 130.130.0.1 > ????? nameservers: > ???????

Can you run the debug script, that might give me more info. https://github.com/thctlo/samba4/raw/master/samba-collect-debug-info.sh Anonimze where needed. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > L.P.H. van Belle via samba > Verzonden: maandag 2 maart 2020 16:23 > Aan: samba at lists.samba.org >

Sorry Paully, I thought i already replied it. The configs look good. Did a look back in time.. And Ahh.. Now this i missed. * yesterday, we changed the IP addresses of our DCs and the Wiki page did not mention (IMHO) 2 critical things... ... So you even missed more. Review all DNS entries for the problem DC and review your AD again. rgrep /etc and /var for all the old ip numbers and/or

On 26/01/15 15:16, Paul Littlefield wrote: > On 26/01/15 15:08, Rowland Penny wrote: >> Yes, set up a new DC with your new OS and join this to the domain, >> once up and running, transfer the seven (yes, there are 7) FSMO roles >> to the new DC. Once everything is running ok, turn off the old DC and >> remove *all* mention of it from the domain. > > Hi Rowland

On 03/02/2020 18:49, Kris Lou via samba wrote: > > From windows: > echo %logonserver% \\DC3 > nltest /dsgetdc:<domain> DC:\\DC3 Address: \\192.168.0.218 Dom Guid: bla bla bla ... The command completed successfully. > From a *nix domain member (i.e. client, not DC): > wbinfo --getdcname=<domain> > winbind --ping-dc wbinfo --getdcname=MYDOMAIN DC3 wbinfo

For some reason, the provision picked up 2 network IP addresses in my VM. Snipped output below... root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 dwVersion : 0xece0205 fBootMethod : DNS_BOOT_METHOD_DIRECTORY fAdminConfigured : FALSE fAllowUpdate : TRUE fDsAvailable : TRUE

On 16/02/2020 15:03, Paul Littlefield via samba wrote: > 1) finding a way for ALL 70+ desktops to look up the DCs properly and switch to a running one if one is not available (otherwise what's the point right?) Hello Samba Mailing List, Just to be clear, I am using Ubuntu Server 18.04.4 LTS running Samba 4.7.6 on both DCs. Is this the Samba version I should be using for this

Hello Samba List, I have 2 problems with dns - seeing the child entries and a zone with an extra octet. First... I have created a /16 reverse zone as per the wiki page (https://wiki.samba.org/index.php/DNS_Administration#To_create_a_.2F24_reverse_zone)... $ samba-tool dns zonecreate dc3 130.130.in-addr.arpa $ samba-tool dns zonelist --reverse dc3 pszZoneName :

I am planning to upgrade the DCs using the join and promote method. List of DCs ----------- 1) SAMBA1 2) SAMBA2 3) DC1 4) DC2 Currently SAMBA1 is the PDC and SAMBA2 is the "SDC" and are in sync with replication and rsync sysvol. DCs SAMBA1 and SAMBA2 are 4.1 git releases with AD Schema version 47. My plan to get to AD Schema version 69 was... 0. Add entries to the DHCP Server for the

On 09/03/18 13:30, lingpanda101 via samba wrote: > On 3/9/2018 5:30 AM, Paul Littlefield via samba wrote: >> For some reason, the provision picked up 2 network IP addresses in my VM. >> >> Snipped output below... >> >> >> root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 >>   dwVersion                   : 0xece0205 >>  

On 02/03/2020 13:36, Paul Littlefield wrote: > On 02/03/2020 13:16, Rowland Penny via samba wrote: >> >> Samba runs samba_dnsupgrade on a regular basis, using dns_update_list >> as a template. Amongst the list of dns entries is this: >> >> AAAA ${HOSTNAME}?????????????????????????????????????????? $IP >> > > Hi Rowland, > > Can I change any of

Hello List, I have a special L2 VPN connected samba deployment setup and I want to make sure the name resolution arrangement is the best for the network. Setup : network 1 + Samba1<<SAME IP range>> <L2 VPN> network2 <<SAME IP range>> + Samba2 I have noticed that the wins server and wins support options are non-inclusive. Samba2: name resolve order =

Guys, what i noticed. Look at this. Refused- 1/3/0 (Class 254) ( /24 ) Paully used /16 update 1/3/1 (Class 254) CNAME V-RDS02.mydomain.com CNAME ? And, if he uses in his example samba-tool dns add dc3 mydomain.com V-RDS02 A 130.130.0.252 A record was used. Is resolv.conf checked and it is sure in pointing to the correct DNS of the AD first? addresses: -

Hello, When I run the following command... $ samba-tool dns add dc3 mydomain.com V-INT A 130.130.0.202 ...I get the following error... ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 176, in _run return self.run(*args, **kwargs) File

On 01/02/2020 15:10, Rowland penny via samba wrote: > Not really, all Samba AD DC's are global catalogs ;-) Ah, OK... so we don't need to worry about that then? -- Paul Littlefield Telephone: 07801 125705 Email: info at paully.co.uk Wiki: http://wiki.indie-it.com/wiki/Special:AllPages LinkedIn: https://www.linkedin.com/in/paullittlefield Paul Littlefield is environmentally

My reverse zones have PTR records. Though I don't have NS records for all of my DC's. I guess that needs to be manually created. Also, you don't have any CNAMES or domain overrides pointing to a single DC? Perhaps Bind is pointing to another internal DNS server, and then to a public DNS? ---- Here's a way to test failover from a Windows client: You can switch logon servers

On 13/02/2020 13:11, Paul Littlefield wrote: > On 12/02/2020 13:08, Rowland penny via samba wrote: >> The first is that a DC must use itself as its nameserver and if >> something goes wrong e.g. Samba has fallen over, then there isn't >> much point having another nameserver, Samba isn't going to use it >> >> The second is, it will not hurt having a second

Hi Gavin and I appear to have successfully connected our Linux and Windows machines via Tinc, but cannot seem to do anything else. We cannot ping each other's vpn network. Gavin would like to be able to: * browse my local SMB (Windows and Samba) network * collect his email via my local mail server Are asking too much of a VPN here? Have we missed something? All details, Linux output and