Displaying 20 results from an estimated 664 matches for "dc01".
2019 Jan 10
2
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...u.
> With the script dropped in straight off Wiki, the errors are now as
> follow. NOTE: the script does, of course, provide at least an exit
> code here. Also, nothing else was generated in samba-ad-dc or bind9
> logs during this operation:
It only logs to syslog
>Jan 10 14:31:46 dc01 dhcpd[1123]: Commit:
> IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
From here on the script should be run
> Jan 10 14:31:46 dc01 sh[1123]: /usr/local/bin/dhcp-dyndns.sh: line 10:
> samba: command not found
Ah, you are (if I remember correctly) using a self compiled Samba...
2019 Jan 11
2
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...n't in /usr/local and then try again.
> Here it is with script properly configured.
> Regarding the later lines having to do with the script, I clearly don't know what exactly is causing them. But surely they are all
> somehow part of this update process?
>
> Jan 10 15:46:23 dc01 dhcpd[1208]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
> Jan 10 15:46:23 dc01 dhcpd[1208]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
> Jan 10 15:46:23 dc01 dhcpd[1208]: execute_statement argv[1] = add
> Jan 10 15:46:23 dc01 dhcpd[1208]: execute_state...
2019 Jan 10
2
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
On Thu, 10 Jan 2019 20:18:37 +0000 (UTC)
Billy Bob <billysbobs at yahoo.com> wrote:
>
>
> On Thursday, January 10, 2019 2:08 PM, Billy Bob via samba
> <samba at lists.samba.org> wrote:
> >Do you want to change your scripts to match my scripts as found on
> >the wiki ?
> >I know they work, well they have for me for the last 6 years.
>
>
2019 Jan 11
0
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...e is coming from, but it isn't from the dhcp scripts.
>
I don't know what to tell you, Rowland. The previous logs were with the -d option in place, and those extra lines were what was added as a result of the -d option.
Here is what the logs show WITHOUT the -d option:
Jan 11 10:00:36 dc01 dhcpd[1704]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[1] = add
Jan 11 10:00:36 dc01 dhcpd[1704]: execute_statement argv[2] =...
2019 Jan 10
0
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...or prefix if Samba isn't in /usr/local
>and then try again.
Here it is with script properly configured.
Regarding the later lines having to do with the script, I clearly don't know what exactly is causing them. But surely they are all somehow part of this update process?
Jan 10 15:46:23 dc01 dhcpd[1208]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
Jan 10 15:46:23 dc01 dhcpd[1208]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
Jan 10 15:46:23 dc01 dhcpd[1208]: execute_statement argv[1] = add
Jan 10 15:46:23 dc01 dhcpd[1208]: execute_statement argv[2] =...
2019 Jan 10
0
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...work.
>
>Rowland
I absolutely agree with you.
With the script dropped in straight off Wiki, the errors are now as follow. NOTE: the script does, of course, provide at least an exit code here. Also, nothing else was generated in samba-ad-dc or bind9 logs during this operation:
Jan 10 14:31:46 dc01 dhcpd[1123]: Commit: IP: 172.20.10.165 DHCID: 1:d4:be:d9:22:9f:7d Name: mgmt01
Jan 10 14:31:46 dc01 sh[1123]: /usr/local/bin/dhcp-dyndns.sh: line 10: samba: command not found
Jan 10 14:31:46 dc01 dhcpd[1123]: execute_statement argv[0] = /usr/local/bin/dhcp-dyndns.sh
Jan 10 14:31:46 dc01 dhcpd[1123]...
2019 Jan 11
3
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
On Friday, January 11, 2019 1:39 PM, Rowland Penny via samba <samba at lists.samba.org> wrote:
> There doesn't seem to be anything really wrong there,the only really
> difference between your named.conf and mine is that I have:
>
> dnssec-validation no;
> dnssec-enable no;
> dnssec-lookaside no;
> listen-on-v6 { none; };
> listen-on port 53
2015 Feb 04
2
DC01 log entries
I run "logcheck" on my servers and have noticed that my DC01 log has
these:
Feb 4 06:58:16 dc01 named[2096]: validating @0xb1c75c18: . NS: got
insecure response; parent indicates it should be secure
Feb 4 06:58:16 dc01 named[2096]: error (insecurity proof failed)
resolving './NS/IN': 208.67.222.222#53
Feb 4 06:58:16 dc01 named[2096]: validating @0x...
2019 Jan 07
4
dns_tkey_gssnegotiate: TKEY is unacceptable
...9;--sysconfdir=/etc' ... '--sysconfdir=/etc/bind' ....
I am following the Samba Wiki for guidiance.
The installation proceeded without error in all tests until I attempted to run:
$ sudo samba_dnsupdate --verbose --all-names
which returned:
IPs: ['172.20.10.130']
force update: A dc01.corp.<DOMAIN>.com 172.20.10.130
* * * * *
29 DNS updates and 0 DNS deletes needed
Successfully obtained Kerberos ticket to DNS/dc01.corp.<DOMAIN>.com as DC01$
update(nsupdate): A dc01.corp.<DOMAIN>.com 172.20.10.130
Calling nsupdate for A dc01.corp.<DOMAIN>.com 172.20.10.13...
2017 Mar 13
3
AD replication issue
On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote:
> Upgraded to 4.6.0 on all nodes. Still seeing the same issue.
>
> If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't
> replicate. If I create it on vsc-dc01 (PDC emulator) then it does
> replicate.
>
> On 03/13/2017 12:13 PM, Arthur Ramsey wrote:
>>
>> I believe the problem is a lack of outbound replication for non PDC
>> emulator DCs. You'll n...
2017 Mar 13
2
AD replication issue
...C
emulator DCs. You'll notice isn't even trying because last successful
was epoch (never) yet there are no errors. Inbound replication for this
DC seems fine.
[root at vsc-dc02 ~]# samba-tool drs showrepl
[...]==== OUTBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
aws\AWS-DC01 via RPC
DSA object GUID: 8b750a53-3d39-4bc0-8fe9-9bffa9e413aa
Last attempt@ NTTIME(0) was successful
0 consecutive failure(s).
Last success @ NTTIME(0)
DC=DomainDnsZones,DC=mediture,DC=dom
epo\EPO-DC01 via RPC
DSA object GUID: 28f7281f-3955-4885-8a7d-42a36ee87590
Last attempt@ NTTIME...
2017 Mar 14
2
AD replication issue
Changes replicate to it, but not from it.
vsc\VSC-DC02
DSA Options: 0x00000001
DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb
DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378
==== INBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=mediture,DC=dom
vsc\DC01 via RPC
DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
Last attempt @ Tue Mar 14 09:26:12 2017 CDT was successful
0 consecutive failure(s).
Last success @ Tue Mar 14 09:26:12 2017 CDT
DC=DomainDnsZones,DC=mediture,DC=dom...
2017 Mar 13
5
AD replication issue
I forgot to associate inter-site links (all using default), which fixed
a lot though I'm still having an issue.
* vsc site
o vsc-dc01
o vsc-dc02
* aws site
o aws-dc01
* epo site
o epo-dc01
* vsc-dc01 => anywhere: OK
* vsc-dc02 => anywhere: not replicating
* aws-dc01 => anywhere: OK
* epo-dc01 => anywhere: OK
I've tried with samba_kcc = false and true.
Thanks,
Arthur
This e-mail a...
2018 May 04
1
unexplained Replication failures...?
Hi Denis,
Thanks for taking the time to answer.
Yes, I may have been wrong with --forced-sync and --full-sync since the
start but in fact I wanted to make sure to force replication between the
servers.
Here is what I have noticed:
- replication works from dc00 -> dc00 but not from dc01 -> dc00:
[root at dc00 ~]# samba-tool drs replicate DC01 DC00
dc=ad,dc=lasthome,dc=solace,dc=krynn --sync-forced --full-sync
Replicate from DC00 to DC01 was successful.
[root at dc00 ~]# samba-tool drs replicate DC00 DC01
dc=ad,dc=lasthome,dc=solace,dc=krynn --sync-forced --full-sync
ERROR(&l...
2015 Sep 03
0
Reverse domain
...I have already told you this, you must
create the reverse zone, it is not created for you, use samba-tool.
You do not add the reverse zone to the name flat files it goes in AD.
And finally, the dhcp set up you say I 'cobbled together' works, it
leads to logs like this:
Sep 3 20:49:38 dc01 dhcpd: Commit: IP: 192.168.0.119 DHCID:
1:84:a6:c8:3b:da:7b Name: ThinkPad
Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[0] =
/usr/local/sbin/dhcp-dyndns.sh
Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[1] = add
Sep 3 20:49:38 dc01 dhcpd: execute_statement argv[2] = 192.168.0.119
Sep...
2018 May 03
2
unexplained Replication failures...?
Hi all,
I'm running in circles trying to debug replication failures on samba
4.7.6:
dc00 : is a VM on KVM host (attached to a bridge on local LAN)
dc01 : is a similarly configured VM on another KVM host.
I've forcibly demoted and re-promoted dc01 but I still cannot get
automatic replication to work:
root at dc00 ~]# samba-tool drs showrepl
Krynn\DC00
DSA Options: 0x00000001
DSA object GUID: 204cb904-754b-4457-af09-9347f8714006
DSA invocatio...
2019 Jan 10
1
samba_dnsupdate options: --use-samba-tool vs. --use-nsupdate, and dhcpd dynamic updates
...considered, in addition to the smb.conf change, in addressing the current issue.===================================
CURRENT SMB.CONF
/usr/local/samba/etc/smb.conf
===================================
[global]
bind interfaces only = Yes
interfaces = lo eno1
netbios name = DC01
realm = CORP.<DOMAIN>.COM
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate
workgroup = CORP
idmap_ldb:use rfc2307 = yes
dns update command = /u...
2017 Mar 14
0
AD replication issue
...te to it, but not from it.
>
> vsc\VSC-DC02
> DSA Options: 0x00000001
> DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb
> DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378
>
> ==== INBOUND NEIGHBORS ====
>
> DC=DomainDnsZones,DC=mediture,DC=dom
> vsc\DC01 via RPC
> DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2
> Last attempt @ Tue Mar 14 09:26:12 2017 CDT was
> successful
> 0 consecutive failure(s).
> Last success @ Tue Mar 14 09:26:12 2017 CDT
>
> DC=Domai...
2015 Feb 06
0
DC01 log entries
...what happens.
or.. disable dnssec in bind9
Louis
>-----Oorspronkelijk bericht-----
>Van: bob at donelsontrophy.net
>[mailto:samba-bounces at lists.samba.org] Namens Bob of Donelson Trophy
>Verzonden: woensdag 4 februari 2015 15:05
>Aan: SAMBA MailList
>Onderwerp: [Samba] DC01 log entries
>
>
>
>I run "logcheck" on my servers and have noticed that my DC01 log has
>these:
>
>Feb 4 06:58:16 dc01 named[2096]: validating @0xb1c75c18: . NS: got
>insecure response; parent indicates it should be secure
>Feb 4 06:58:16 dc01 named[2096]: err...
2015 Sep 03
2
Reverse domain
How is the reversed domain handled, or is it not. Rowland, you did not
have that in your sample you cobbled together.
In /usr/share/samba/setup/named.conf there is:
zone "123.168.192.in-addr.arpa" in {
type master;
file "123.168.192.in-addr.arpa.zone";
update-policy {
grant ${REALM_WC} wildcard *.123.168.192.in-addr.arpa. PTR;