similar to: DNS issues after FSMO seize

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

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 3/31/2016 3:12 PM, IT Admin wrote: > Aaaaaaand more problems... Welcome to the continuing saga of FILER. > > It appears that neither SOA or NS records were updated during the process > of moving fsmo roles to CBADC01. SOA entries on all three active DCs point > to FILER. There aren't any NS records for any of the new DCs, only FILER. > In RSAT each DNS server's

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. > 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. Sorry, but this, as

Alright... appreciate the info. Gave it a shot. Domain is still up but shares are down because they were hosted on FILER which has now been demoted and is no longer running any samba services. What I did while following the wiki "Transfer/Seize FSMO Roles": 1) logged on to FILER, ran samba-tool fsmo show, verified all 7 roles were owned by FILER. 2) logged on to CBADC01, executed

Aaaaaaand more problems... Welcome to the continuing saga of FILER. It appears that neither SOA or NS records were updated during the process of moving fsmo roles to CBADC01. SOA entries on all three active DCs point to FILER. There aren't any NS records for any of the new DCs, only FILER. In RSAT each DNS server's properties show filer.cb.cliffbells.com is the primary server. This

I ran ldbsearch on my sam.ldb I searched for CBADC02, CBADC03, and TESTES (all VMs that fail to join domain), results are below: CBADC02 shows up a few times: # record 1906 dn: CN=CBADC02\0ADEL:de85228c-f92b-4d5d-9d6a-01c3f915dec9,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu$ objectClass: top objectClass: server instanceType: 4 whenCreated: 20160310044543.0Z uSNCreated: 4215

>> 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

"I expect you don't have just copied your VMs disks without changing VMs hostname and FQDN. I expect you don't fully re-use smb.conf from another DC (you can do that but you must change hostname into smb.conf)." 1) These are new Ubuntu VMs, not cloned, built from scratch. I tried joining them with no smb.conf in /usr/local/samba/etc You have disabled SELinux too 2) AFAIK

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

No dice. Logged in to a workstation with RSAT installed. Added computer to OU Domain Controllers, closed ADUC, attempted join again. itwerks at cbadc03:~$ kinit Administrator Password for Administrator at CB.CLIFFBELLS.COM: itwerks at cbadc03:~$ klist -e Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: Administrator at CB.CLIFFBELLS.COM Valid starting Expires Service

Sorry, I meant to include the command you sent in my last message, I had executed it while troubleshooting... :~$ sudo /usr/local/samba/bin/ldbsearch --cross-ncs -H /usr/local/samba/private/sam.ldb '(fsmoroleowner=*)' | grep 'dn:' | sed 's|dn: ||' CN=Schema,CN=Configuration,DC=cb,DC=cliffbells,DC=com CN=Partitions,CN=Configuration,DC=cb,DC=cliffbells,DC=com

Hi Rowland, I had run those queries during troubleshooting last night as well, apologies if I get ahead of myself, here are all of my missing roles, they only have dn entries, the second line containing fsmoowner is blank: itwerks at cbadc01:~$ sudo /usr/local/samba/bin/ldbsearch -H /usr/local/samba/private/sam.ldb -b 'CN=System,DC=cb,DC=cliffbells,DC=com' -s sub

On 22/03/2023 01:04, Anantha Raghava via samba wrote: > Hi, > > While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a > peculiar problem. AD Component is up, but DNS is just not coming up. > kinit is reporting KDC not found problem. > > All these years I have been compiling samba from source and for nearly 7 > years, it was working like a charm. But this

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

Hi, While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a peculiar problem. AD Component is up, but DNS is just not coming up. kinit is reporting KDC not found problem. All these years I have been compiling samba from source and for nearly 7 years, it was working like a charm. But this upgrade activity, we ran into rough weather. We do not upgrade the existing servers where as,

Hello Rowland, ldbsearch command is returning 0 records. # returned 0 records # 0 entries # 0 referrals On the backup front, I take the back up using samba-tool backup command and it was successful. Can I create a new ForestZone using samba-tool? I asking this question as RSAT is not connecting to DNS server. Thanks & Regards, Anantha Raghava H A This e-mail communication and any

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

On 28/03/16 09:09, IT Admin wrote: > Alright... appreciate the info. Gave it a shot. Domain is still up > but shares are down because they were hosted on FILER which has now > been demoted and is no longer running any samba services. > > What I did while following the wiki "Transfer/Seize FSMO Roles": > > 1) logged on to FILER, ran samba-tool fsmo show, verified

I cannot join two new VMs to my domain, I receive the following error on both machines: twerks at cbadc03:~$ kinit Administrator Password for Administrator at CB.CLIFFBELLS.COM: itwerks at cbadc03:~$ klist -e Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: Administrator at CB.CLIFFBELLS.COM Valid starting Expires Service principal 03/21/2016 00:19:56 03/21/2016