similar to: Missing new NS record.

Yes I shut down the original DC, and noticed most of the AD relient services were hanging, and I think the culprit was DNS on the new DC. Would you guys recommend waiting for 4.5, or switching to the BIND backend? The only reason that I chose the internal DNS server in the first place was that I thought Kai said the BIND side wasn't getting as much love these days. On Thu, Aug 18, 2016 at

Anyway NS records are used when DNS server speak to DNS server, not by clients. So AD would work just fine without them. NS are used when a client ask something the configured resolver can't resolve by himself and when the resolver is not configured to forward request to relevant DNS server. IE: client search for toto.org and its resolver does not know anything about that zone. Resolver will

On Thu, 18 Aug 2016 16:59:51 +0200 mathias dufresne via samba <samba at lists.samba.org> wrote: > Hi, > > I never had a look on MS AD regarding that, to check if NS record is > created for each DC running DNS service or not. I couldn't find anything that explicitly says that each DC should have its own SOA in AD. What I could find was that each AD-integrated zone on a DC

On 05/03/16 04:54, Allen Chen wrote: > On 2/29/2016 4:10 AM, Rowland penny wrote: >> On 28/02/16 23:05, Reindl Harald wrote: >>> >>> >>> Am 28.02.2016 um 23:54 schrieb Rowland penny: >>>> On 28/02/16 22:42, Reindl Harald wrote: >>>>> >>>>> >>>>> Am 28.02.2016 um 23:10 schrieb Rowland penny:

Hi, I never had a look on MS AD regarding that, to check if NS record is created for each DC running DNS service or not. Anyway Samba AD does not create them and that's not an issue as long as you don't plan to make your AD DNS zones public (available on the Internet). As far as I understood DNS, during DNS resolution, NS is used only when client's resolver does not know how to

On Wed Jul 8 13:46:41 UTC 2020, Rowland penny wrote: > > This is because it is an 'A' record and not an 'NS' record. samba-tool dns delete localhost brockley.harte-lyne.ca brockley.harte-lyne.ca. A 192.168.216.162 -U administrator Password for [BROCKLEY\administrator]: ERROR(runtime): uncaught exception - (9701, 'WERR_DNS_ERROR_RECORD_DOES_NOT_EXIST') File

I'm just curious how this works. I've set up an Active Directory Domain controller using Samba 4.0.0. I DO NOT have Winbind configured. When I run "ls -al /samba/share/directory" I notice that I have users named like 3000000 belonging to the group "users". Without windbind configured, how do I have users and groups inside of my Samba domain (for instance the

2016-04-04 14:20 GMT+02:00 Rowland penny <rpenny at samba.org>: > On 04/04/16 10:23, mathias dufresne wrote: > >> SOA means "this DNS se'rver can modify the zone". >> > > No it doesn't, it stands for 'Start Of Authority' and contains who to > contact for the domain records. > Rowland... thank you again Captain Obvious. Yes SOA means

>>> >>> Can I suggest that you do what I did, create your own small test >>> domain in VMs using Bind9 >> >> Yes, that is a good idea. However, from what I had read before, much >> of it on the Samba wiki, I was expecting Samba4 to just work with >> multiple DCs. I still wonder why no one ever seems to have tested or >> questioned that

On 07.07.2020 21:14, Rowland penny via samba wrote: > On 07/07/2020 20:00, James B. Byrne via samba wrote: >> I have this on the DC smb4-1.brockley.harte-lyne.ca: >> >> samba-tool dns query localhost brockley.harte-lyne.ca >> brockley.harte-lyne.ca >> ALL -U administrator >> Password for [BROCKLEY\administrator]: >> ?? Name=, Records=6, Children=0

As I already wrote here, the fact NS is not automatically filled is not an issue as long as you don't plan to make your AD a public thing. AD is not meant to be public, not really, or at least: not often. Let's say you want to make your DNS zones public anyway (not the whole AD). Will you make all your DC a public name server or will you before think about what you are about to do and

Hello, My domain was provisioned using a Windows 2008R2 server as the first DC, and I then subsequently joined a Samba 4.4.2 DC running on Ubuntu 14.04.4 and using BIND 9.9.5 as the DNS backend. Everything seems to be working properly after I added an NC replica for the zones as per the troubleshooting page. All zones resolve and replicate properly, but I noticed that there are no NS records

2016-10-18 15:25 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Tue, 18 Oct 2016 14:59:31 +0200 > mathias dufresne via samba <samba at lists.samba.org> wrote: > > > Anyway NS records are used when DNS server speak to DNS server, not by > > clients. So AD would work just fine without them. > > > > NS are used when a client ask

On 02/12/15 11:59, mathias dufresne wrote: > Rowland, > > What did you request as DNS? Samba + Bind + DLZ ? > If yes, the fact your two DNS are replying "I am SOA" is a feature from > Bind9 or from DLZ patch. Yes, I use bind9 with the dlz backend. > > That's important as a standard Samba AD designed without Bind is using LDAP > defined entry for SOA. Asking

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Paul > R. Ganci via samba > Verzonden: woensdag 1 januari 2020 23:49 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Cannot remove old NS record > > On 12/22/19 12:07 PM, Rowland penny via samba wrote: > >> > >> Are there any suggestions to

I'm pretty new to compiling software, although I would rather compile my own Samba 4.0.0 server rather than wait for it to become available in the repositories of my distribution. How do you update compiled software. Like if I compile and install Samba 4.0.0, and then 4.0.1 comes out, Is there a way to update to that without starting from scratch and having to rebuild my domain? Thanks

I have this on the DC smb4-1.brockley.harte-lyne.ca: samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca ALL -U administrator Password for [BROCKLEY\administrator]: Name=, Records=6, Children=0 SOA: serial=7, refresh=900, retry=600, expire=86400, minttl=3600, ns=SMB4-1.brockley.harte-lyne.ca., email=support.harte-lyne.ca. (flags=600000f0, serial=110, ttl=3600)

Once both DC were rebooted, after the MS Windows was also rebooted (here I could have just wait I think) this MS Windows client is connecting on DC from its AD Site again. 2015-12-23 16:51 GMT+01:00 mathias dufresne <infractory at gmail.com>: > Hi all, > > Firs I apologize I did not manage to find time to reply earlier. > > The initial issue was about how Samba AD react when

On 02/12/15 10:31, mj wrote: >> I can find on the internet multiple instances of 'every DC running dns >> should have a SOA record', but I cannot find any concrete examples of an >> ldif that shows this. Does each DC have a separate SOA record in AD, or >> is there just one SOA record and the DC just claims to be the SOA, or is >> there just one SOA record

Hi all, Wish you a happy new year altogether! Mathias, James, let me first say that I highly appreciate your help with all your testing and writing up your thoughts. Here are my responses: A. I have no different sites, no various subnets; so I don't really know what to do. B. I don't understand the purpose of setting my domain up with different sites with associated networks, if on