search for: dnsupdates

On Sun, 31 Mar 2019 13:55:18 +0200 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> > wrote: > > > > you can upgrade from 4.7 to 4.9. > > but you must run samba-tool dbcheck > > that should work also. after the check run samba-tool dbcheck > > --reindex > > I

you can upgrade from 4.7 to 4.9. but you must run samba-tool dbcheck that should work also. after the check run samba-tool dbcheck --reindex Main difference, a few depends and there versions. debian has tracker 1.0, ubuntu tracker 2.0 for example. Greetz Louis Op 30 mrt. 2019, om 16:20, Viktor Trojanovic <viktor at troja.ch> schreef: Thanks Louis, appreciate it! The main reason

On Sun, 31 Mar 2019 14:29:32 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Sun, 31 Mar 2019 13:55:18 +0200 > > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > > > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle

On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> wrote: > > you can upgrade from 4.7 to 4.9. > but you must run samba-tool dbcheck > that should work also. after the check run samba-tool dbcheck --reindex > I thought that maybe indeed I did something wrong the last time so I followed your advice. Unfortunately, it broke my DC again. (Luckily, I made a

Hi, I use the Van Bell repo, I've upgraded from samba 4.7 to samba 4.9 but now it fails, these are the errors: dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: [2018/12/12 09:14:49.372290, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) dic 12 09:14:49 samba4 samba[4881]: task[dnsupdate][4881]: /usr/sbin/samba_dnsupdate: Failed to bind to uuid

Hello! After upgrade Samba, dont work more. Dns is ok(I Use bind). I have Two Severs, i  updated the second(dont having fsmo). Any Help ? Regards; Information; samba -V Version 4.6.3 ----- SO: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 14.04.2 LTS Release:        14.04 Codename:       trusty ----- Samba option: ./configure    

On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 31 Mar 2019 13:55:18 +0200 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle <belle at bazuin.nl> > > wrote: > > > > > > you can upgrade from 4.7 to 4.9. > > > but

Hi all, Using help of configure script we can found taht: --with-dnsupdate Build with dnsupdate support (default=yes) what does taht really enable/disable? A - Is this option related to DC only? A1 - Is this to allow internal DNS to support DNS updates? A2- Is this to allow all DNS sub-system to support DNS updates? B - Is this for Samba as AD client?

I followed this url to set up Samba AD DC. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt I do have it working. I am testing with a Windows 10 VM as a member of the domain. The machine joins the domain. Also, as administrator, I can create and enforce Group Policies. from this Windows machine. I have a Fedora 29 server which serves DHCP and DNS (and

Am 02.07.19 um 16:24 schrieb Stefan G. Weichinger via samba: > Am 02.07.19 um 16:09 schrieb Stefan G. Weichinger via samba: >> >> I get problems with group policies not applied ... seems an older >> problem surfacing now. >> >> Before I debug at current level I consider upgrading the 2 DCs from >> 4.8.12 (Debian Stretch) to 4.9.9 >> >> Anything

Thanks Louis; /etc/krb5.conf [libdefaults] default_realm = EXAMPLE.COM dns_lookup_realm = false dns_lookup_kdc = true /etc/resolv.conf search example.com nameserver 192.168.50.40 /etc/hosts 127.0.0.1 localhost samba4.example.com 192.168.50.40 samba4.example.com samba4 ldap.example.com Output off: samba-tool dbcheck --cross-ncs NOTE: old (due to rename

On 03/08/2019 03:01, Patrik via samba wrote: > My config is this: > # Global parameters > [global] > # bind interfaces only = Yes > # if this is turned on, always perfect > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 > #

On Sun, 31 Mar 2019 at 14:45, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 31 Mar 2019 14:29:32 +0200 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Sun, 31 Mar 2019 13:55:18 +0200 > > >

I upgrade our samba3 server to the latest samba4. Everything is working except for the dnsupdate: > /usr/local/samba/sbin/samba_dnsupdate --verbose --all-names: IPs: ['172.x.x.x'] Traceback (most recent call last): File "/usr/local/samba/sbin/samba_dnsupdate", line 508, in <module> get_credentials(lp) File "/usr/local/samba/sbin/samba_dnsupdate", line

> > I followed this url to set up Samba AD DC. > > https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18. > 04-samba-AD_DC.txt > > > > I do have it working. I am testing with a Windows 10 VM as a member > > of the domain. > > The machine joins the domain. Also, as administrator, I can create > > and enforce > > Group Policies. from

On 05/04/16 20:23, Rowland penny wrote: (I understand this might be specific to FreeBSD, but I asked on its mailing list and got no answer...) >> Then why is it an option *in alternative* to BIND? > > What do you mean '*in alternative*' ?? I mean when I build Samba port, I can choose NSUPDATE *or* BIND99 *or* BIN910 (where "or" means "exclusive or",

On 03/08/2019 11:17, Patrik wrote: > the problem is that dnsupdate is not working becuase i use dlz. i > cannot use dbsupdate with dnsupdate it fails. > *_ > _* What is 'dbsupdate' ? I can assure you that dnsupdate does work with dlz. I think you need to give us more info. Rowland

Hai, Can you post /etc/krb5.conf /etc/resolv.conf /etc/hosts Output off: samba-tool dbcheck --cross-ncs And last question, are there any DC removed from the domain. 50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=> 192.168.50.40] My guess here the UUID is a removed DC. You samba config looks fine to me. Greetz, Louis > -----Oorspronkelijk bericht----- >

Hello, I'm in trouble here with what appears to be a total meltdown of my DNS on my Domain Controllers. I only have two DCs right now and I cannot resolve anything on either of them. I am on Ubuntu 16.04 with a compiled version of Samba 4.10.4. I also have a compiled version of BIND 9.10.3-P4-Ubuntu <id:ebd72b3> # service bind9 status ? bind9.service - BIND Domain Name Server ?

...icated DNS process samba_dnsupdate --use-samba-tool By the way, is your /etc/resolv.conf pointing to yourself? Is your /etc/krb5.conf and /var/lib/samba/private/krb5.conf identical? Denis > can move FSMO. But DNS if working only on DC1, not on DC2, > I have found in logs troubles with dnsupdates. DC1 thinks it is only one > DC in domain. > > _ldap._tcp.Default-First-Site._sites.gc._msdcs.test.local. 900 IN SRV 0 > 100 3268 dc2.test.local. > tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor > code may provide more information, Minor = KDC has no supp...