search for: soas

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

On 01/03/16 13:23, Reindl Harald wrote: > > > Am 01.03.2016 um 11:23 schrieb mathias dufresne: >> Several SOA is easy to design without breaking RFC: as every DNS server >> in AD is able to modify the zone, every DNS server in AD is SOA. As any >> DNS server is SOA and only one SOA can be returned, these DNS server >> must reply "I am SOA". >> 10 DC

Hi all, I am experiencing strange behaviour regarding DNS resolution with my samba-driven AD. This is with Debian-packaged samba on raspberry Pi: # samba -V Version 4.19.5-Debian # uname -a Linux dc3.ad.mydomain.tld 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux I would expect that every DNS server of the domain would respond with the same SOA record. But

For me: - SOA means where updates can be sent. - SOA can be one or several. - NS is a record to help non-authoritative name servers to find a valid name server for the zone they receive a request and they don't know anything about that zone. - SOA is often declared as NS, I agree. I explained this is not mandatory. There is no link between these two notions except they share a zone. You are

2016-02-29 0:05 GMT+01:00 Reindl Harald <h.reindl at thelounge.net>: > > > 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: >>> >>>> On 28/02/16 21:56, Reindl Harald wrote: >>>> >>>>>

On 05/04/16 13:48, lingpanda101 at gmail.com wrote: > On 4/5/2016 8:17 AM, mathias dufresne wrote: >> For me: >> - SOA means where updates can be sent. >> - SOA can be one or several. >> - NS is a record to help non-authoritative name servers to find a valid >> name server for the zone they receive a request and they don't know >> anything about that

Ok Mathias.. I hoop this helps a bit. https://technet.microsoft.com/nl-nl/library/cc816941(v=ws.10).aspx now type : nslookup -type=soa internal.domain.tld or nslookup -debug -type=soa internal.domain.tld and look at nslookup -debug -type=soa internal.domain.tld ip_of_a_NS1-server. nslookup -debug -type=soa internal.domain.tld ip_of_a_NS2-server. And see.. The soa record contains only

SOA means "this DNS se'rver can modify the zone". Using Bind-DLZ all DNS servers can modify the AD zones, they all reply "I am the SOA" when you ask them about SOA for AD zones. Using Internal DNS I expect all DNS servers can modify the AD zones also (that's internal stuff) but even if they can modify the AD zone locally that's is not the process chosen by Samba

>> There is no link between SOA and NS except they share the zone.... Really... ? i dont agree.. SOA specifies the DNS server providing authoritative information about a domain, so looks to me its direcly related to NameServers. SOA contains the primary (NS) server of the domain. Looks to me its related... Below it nice explained how DNS works. That a SOA not (always) related is

On 29/02/16 11:51, Reindl Harald wrote: > > > Am 29.02.2016 um 12:29 schrieb Rowland penny: >> On 29/02/16 10:45, Reindl Harald wrote: >>> >>> >>> Am 29.02.2016 um 11:28 schrieb Rowland penny: >>>> On 29/02/16 09:42, Reindl Harald wrote: >>>>> >>>>> >>>>> Am 29.02.2016 um 10:10 schrieb Rowland penny:

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. I'm running Sernet Samba 4.7 on Ubuntu 16. I noticed that when my first DC went away, I had problems. The SOA record for the domain still points at that first DC. I found, in this entry from 2014 ( https://lists.samba.org/archive/samba/2014-August/184301.html) that "Windows AD servers actually 'lie' about the SOA record, and always say that it points to themselves. So in a

Le 27/05/2019 à 09:50, Rowland penny via samba a écrit : > On 27/05/2019 08:28, Julien TEHERY via samba wrote: >> Hi >> >> I have a setup with 2 DC on a main site, et 14 DCs which are located >> on 7 AD sites. >> I recently noticed in my DNS zones that my SOA record is associated >> to the last DC that was joined to the domain. >> But this DC is

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: >>>> On 28/02/16 21:56, Reindl Harald wrote: >>>>> >>>>> >>>>> Am 28.02.2016 um 22:22 schrieb John

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:

On 01/03/16 14:07, Reindl Harald wrote: > > > Am 01.03.2016 um 14:50 schrieb Rowland penny: >> On 01/03/16 13:23, Reindl Harald wrote: >>> >>> Am 01.03.2016 um 11:23 schrieb mathias dufresne: >>>> Several SOA is easy to design without breaking RFC: as every DNS >>>> server >>>> in AD is able to modify the zone, every DNS server

On 29/02/16 10:45, Reindl Harald wrote: > > > Am 29.02.2016 um 11:28 schrieb Rowland penny: >> On 29/02/16 09:42, Reindl Harald wrote: >>> >>> >>> Am 29.02.2016 um 10:10 schrieb Rowland penny: >>>> Everything you say is valid except for when it comes to AD dns. >>>> When you want data from a zone, you start with the SOA record, you

On 28/02/16 22:42, Reindl Harald wrote: > > > Am 28.02.2016 um 23:10 schrieb Rowland penny: >> On 28/02/16 21:56, Reindl Harald wrote: >>> >>> >>> Am 28.02.2016 um 22:22 schrieb John Gardeniers: >>>> Thanks Rowland. Perhaps because I expected these basic issues to have >>>> been resolved long ago I never thought to check the SOA

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

Hi, We have outdated SOA information in our samba DNS. We used to have a DC1, and it is no more, however it's listed in our SOA records on both remaining DC's. I think this is not correct. I am under the impression that in order to get full failover support, all DC's need to have listed themselves as SOA. This is also what google tells me: