search for: gateway4

...oud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: eth0: dhcp4: false addresses: [192.168.0.11/16] gateway4: 192.168.0.200 nameservers: search: [mydom.samdom.com] addresses: [192.168.0.11, 192.168.0.14, 192.168.0.200] 192.168.0.11 is this server 192.168.0.14 is another AD DC 192.168.0.200 is a router/gateway Thanks, Jonathan Kreider

On 02/03/2020 09:54, Paul Littlefield via samba wrote: > Hello, > > I have some DNS weirdness for you folks to chew on and help me with... > > On Saturday I added this entry... > > $ samba-tool dns add dc3 mydomain.com V-RDS02 A 130.130.0.252 > > but this morning I've come in to the office and the A records have > disappeared to be replaced by AAAA records...

...d 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: > ??????? addresses: > ??????? - 130.130.0.218 > ??????? - 130.130.0.219 > ??????? search: > ??????? - mydomain.com > ????? optional: true > ? version: 2 Samba runs samba_dnsupgrade on a regular basis, using dns_update_list as a template....

...ss 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: - 130.130.0.218/16 gateway4: 130.130.0.1 nameservers: addresses: - 130.130.0.218 - 130.130.0.219 What are these AD-DC's ? - 130.130.0.218 - 130.130.0.219 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.or...

Hi, I hope someone can help me with the following problem. I followed the following guides to setup samba as an additional active directory server to my windows server with bind9 dns: https://www.tecmint.com/join-additio...r-replication/<https://www.tecmint.com/join-additional-ubuntu-dc-to-samba4-ad-dc-failover-replication/>

...m > > I've now changed the nameserver to localhost. This is the netplan yaml config behind this: The 'nameserver' should be the DCs IP, see above > > network: > ethernets: > ens18: > addresses: ['172.17.2.1/16'] > gateway4: 172.17.1.1 > nameservers: > addresses: [127.0.0.1] > search: [domain.com] > version: 2 > > And this is the content of the /etc/bind/named.conf: > > include "/etc/bind/named.conf.options"; > include "/et...

...write a file > # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with > the following: > # network: {config: disabled} > network: > version: 2 > ethernets: > eth0: > dhcp4: false > addresses: [192.168.0.11/16] > gateway4: 192.168.0.200 > nameservers: > search: [mydom.samdom.com] > addresses: [192.168.0.11, 192.168.0.14, 192.168.0.200] > > 192.168.0.11 is this server > 192.168.0.14 is another AD DC > 192.168.0.200 is a router/gateway Nothing wrong wi...

...mba-AD_DC.txt > network: > ? ? ? ? version: 2 > ? ? ? ? ethernets: > ? ? ? ? ? ? ? ? eth0: > ? ? ? ? ? ? ? ? ? ? ? ? dhcp4: no > ? ? ? ? ? ? ? ? ? ? ? ? addresses: [10.199.251.11/24 > <http://10.199.251.11/24>] > ? ? ? ? ? ? ? ? ? ? ? ? gateway4: 10.199.251.1 > ? ? ? ? ? ? ? ? ? ? ? ? nameservers: > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? search: [samdom.example.com > <http://samdom.example.com>] > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? addresses: [10.199.251.10] > > #EOF > > # /run/systemd/resolve/stub-resol...

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

...channel query_logging { syslog daemon; severity dynamic; print-time yes; }; category queries { query_logging; }; }; -------------------- yaml file in /etc/netplan network: version: 2 renderer: NetworkManager ethernets: eno1: dhcp4: no addresses: - 192.168.2.3/22 gateway4: 192.168.1.1 nameservers: search: [thecompumax.com ] addresses: [192.168.2.3, 192.168.2.1, 192.168.1.1] -------------------- /etc/krb5.conf (root:named rw-r--r--) [libdefaults] default_realm = THECOMPUMAX.COM dns_lookup_realm = true dns_lookup_kdc = true [realms] THECOMPUMAX....

...aml The last adresses: needs a server adres. cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: eth0: addresses: [ 192.168.249.31/24 ] gateway4: 192.168.249.1 nameservers: search: [ internal.example.com ] addresses: The corrected version is : cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 render...

...f is managed by netplan under Ubuntu 18: nameserver 127.0.0.53 options edns0 search domain.com I've now changed the nameserver to localhost. This is the netplan yaml config behind this: network: ethernets: ens18: addresses: ['172.17.2.1/16'] gateway4: 172.17.1.1 nameservers: addresses: [127.0.0.1] search: [domain.com] version: 2 And this is the content of the /etc/bind/named.conf: include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include &qu...

...ibes the network interfaces available on your system LPHvBvs> # For more information, see netplan(5). LPHvBvs> network: LPHvBvs> version: 2 LPHvBvs> renderer: networkd LPHvBvs> ethernets: LPHvBvs> eth0: LPHvBvs> addresses: [ 192.168.249.31/24 ] LPHvBvs> gateway4: 192.168.249.1 LPHvBvs> nameservers: LPHvBvs> search: [ internal.example.com ] LPHvBvs> addresses: LPHvBvs> The corrected version is : LPHvBvs> cat /etc/netplan/01-netcfg.yaml LPHvBvs> # This file describes the network interfaces available on your syste...

Hello, ???? Having issues with a DC not responding to DNS requests. OS is Ubuntu 18.04.4 LTS. Samba version 4.12.2 compiled from source. Checking to see what is listening on port 53 reports; @soldc4:~# netstat -tulpn | grep ":53" tcp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????? LISTEN????? 2935/systemd-resolv tcp6?????? 0????? 0 :::53 :::*??????????????????? LISTEN?????

...     Current Scopes: DNS >        LLMNR setting: yes > MulticastDNS setting: no >       DNSSEC setting: no >     DNSSEC supported: no >          DNS Servers: 10.0.0.2 > > and my interface's configuration is > > ens18: >       addresses: [ 10.0.0.3/24 ] >       gateway4: 10.0.0.1 >       nameservers: >           addresses: >               - "10.0.0.2" > > I don't use the other network interface (10.1.0.3), it's not connected > to the same network. > > Regards, > > Vincent > > Le 03/05/2019 à 15:13, L.P.H. v...

...r.arpa            <many others> Link 2 (ens18)       Current Scopes: DNS        LLMNR setting: yes MulticastDNS setting: no       DNSSEC setting: no     DNSSEC supported: no          DNS Servers: 10.0.0.2 and my interface's configuration is ens18:       addresses: [ 10.0.0.3/24 ]       gateway4: 10.0.0.1       nameservers:           addresses:               - "10.0.0.2" I don't use the other network interface (10.1.0.3), it's not connected to the same network. Regards, Vincent Le 03/05/2019 à 15:13, L.P.H. van Belle a écrit : > Hai Vincent, > > Ok, Here it...

...LMNR setting: yes >> MulticastDNS setting: no >>       DNSSEC setting: no >>     DNSSEC supported: no >>          DNS Servers: 10.0.0.2 >> >> and my interface's configuration is >> >> ens18: >>       addresses: [ 10.0.0.3/24 ] >>       gateway4: 10.0.0.1 >>       nameservers: >>           addresses: >>               - "10.0.0.2" >> >> I don't use the other network interface (10.1.0.3), it's not connected >> to the same network. >> >> Regards, >> >> Vincent >&...

...s network configuration capabilities, > write a file > # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with > the following: > # network: {config: disabled} > network: > ??? ethernets: > ??????? enp0s3: > ??????????? addresses: [172.16.23.30/24] > ??????????? gateway4: 172.16.23.201 > ??????????? dhcp4: no > ??????????? nameservers: > ??????????????????? addresses: [172.16.23.30,172.16.23.28] > ??????????????????? search: [domain.local] > > ??? version: 2 > Great that looks fine. Not using : /etc/netplan/01-netcfg.yaml ? That ok if...

Hi, Louis, Rowland, thanks for you answer. @Louis All packages were installed. I change my config file following your advices, the problem is still here. I already followed guides from thctlo's github. @Rowland Yes, my dns domain was different, but answered also to test.lan. It's now set to 'kdc=dc.foo.lab' I have my user vincent with uidNumber 10010 and gidNumber 13010

Following the guidance here, https://wiki.samba.org/index.php/Idmap_config_ad, I added idmap lines to my smb.conf file on my Samba 4.7 AD-DC server on Ubuntu 18.04. Samba no longer starts and testparm reports that the idmap ranges for the default * domain and the AD domain are overlapping. Here's my smb.conf file (FWIW, if I don't comment security = ADS, server role is set to Member