Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[Samba] Non Functioning Internal DNS - Samba4
608 views
Skip to first unread message
Donaldson Jeff
Oct 31, 2014, 11:30:03 AM10/31/14
to
??
Recently one of my Samba4 (4.2.0 Ver) Domain Controllers started acting up. Authentication against it would time out and fail, but until recently the internal DNS was still working. Now the internal DNS fails. If I use nslookup and set the server to it, then look up any hostname I get "connection timed out; no servers could be reached". This DC is my primary and has all FSMO roles. I need to get this working again in order to seize those roles on one of my other DCs. During troubleshooting here are some of the things I found.
If I nslookup the IP address of my primary DC on one of my other servers, I get two records
25.2.xxx.xx.in-addr.arpa name = hostname.
25.2.xxx.xx.in-addr.arpa name = FQDN.
I only get the FQDN when I lookup my other DCs. When I found this, I tried to use Samba-Tool to delete the hostname. record, but I get message that the record doesn't exist. If I then run samba-tool dns serverinfo hostname, I get the following error...
ERROR(runtime): uncaught exception - (-1073741643, 'NT_STATUS_IO_TIMEOUT') File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run
return self.run(*args, **kwargs)
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 703, in run
dns_conn = dns_connect(server, self.lp, self.creds)
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 37, in dns_connect
dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
I then tried checking the sam.ldb to see how the record is entered using ldbedit --url=sam.ldb. When I look at it's record, there are at least 10 additional servicePrincipalName lines that are pointing to an old orphaned DC that I had to manually remove using ADSI and AD Sites and Services several months back. They are somehow attached to the Primary DC record in sam.ldb now. Could this be causing the DNS failure? If so, what if I were to take each DC down (over a weekend of course) then manually edit the record in sam.ldb on each DC making sure that only the one being edited was up at a time, then once all of the changes are complete bring each one back online. The database record would be the same on all DCs and therefore replication wouldn't cause any further damage.
Oddly enough, despite all of this I can still connect to this DC via DNS Manager. Its really slow, but I can see all of the records and even attempted to delete the PTR record for the odd hostname. I got similar error that the record does not exist. I can only assume that there is a timeout querying DNS via nslookup that DNS manager doesn't hit.
Is there anything else I may be missing in troubleshooting this problem? If needed I can provide info from resolv.conf and hosts. Any help is appreciated.
Regards,
Jeff
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Recently one of my Samba4 (4.2.0 Ver) Domain Controllers started acting up. Authentication against it would time out and fail, but until recently the internal DNS was still working. Now the internal DNS fails. If I use nslookup and set the server to it, then look up any hostname I get "connection timed out; no servers could be reached". This DC is my primary and has all FSMO roles. I need to get this working again in order to seize those roles on one of my other DCs. During troubleshooting here are some of the things I found.
If I nslookup the IP address of my primary DC on one of my other servers, I get two records
25.2.xxx.xx.in-addr.arpa name = hostname.
25.2.xxx.xx.in-addr.arpa name = FQDN.
I only get the FQDN when I lookup my other DCs. When I found this, I tried to use Samba-Tool to delete the hostname. record, but I get message that the record doesn't exist. If I then run samba-tool dns serverinfo hostname, I get the following error...
ERROR(runtime): uncaught exception - (-1073741643, 'NT_STATUS_IO_TIMEOUT') File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run
return self.run(*args, **kwargs)
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 703, in run
dns_conn = dns_connect(server, self.lp, self.creds)
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 37, in dns_connect
dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
I then tried checking the sam.ldb to see how the record is entered using ldbedit --url=sam.ldb. When I look at it's record, there are at least 10 additional servicePrincipalName lines that are pointing to an old orphaned DC that I had to manually remove using ADSI and AD Sites and Services several months back. They are somehow attached to the Primary DC record in sam.ldb now. Could this be causing the DNS failure? If so, what if I were to take each DC down (over a weekend of course) then manually edit the record in sam.ldb on each DC making sure that only the one being edited was up at a time, then once all of the changes are complete bring each one back online. The database record would be the same on all DCs and therefore replication wouldn't cause any further damage.
Oddly enough, despite all of this I can still connect to this DC via DNS Manager. Its really slow, but I can see all of the records and even attempted to delete the PTR record for the odd hostname. I got similar error that the record does not exist. I can only assume that there is a timeout querying DNS via nslookup that DNS manager doesn't hit.
Is there anything else I may be missing in troubleshooting this problem? If needed I can provide info from resolv.conf and hosts. Any help is appreciated.
Regards,
Jeff
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Rowland Penny
Nov 1, 2014, 8:00:03 AM11/1/14
to
On 31/10/14 13:55, Donaldson Jeff wrote:
> ??
>
> Recently one of my Samba4 (4.2.0 Ver) Domain Controllers started acting up. Authentication against it would time out and fail, but until recently the internal DNS was still working. Now the internal DNS fails. If I use nslookup and set the server to it, then look up any hostname I get "connection timed out; no servers could be reached". This DC is my primary and has all FSMO roles. I need to get this working again in order to seize those roles on one of my other DCs. During troubleshooting here are some of the things I found.
>
>
> If I nslookup the IP address of my primary DC on one of my other servers, I get two records
>
>
> 25.2.xxx.xx.in-addr.arpa name = hostname.
>
> 25.2.xxx.xx.in-addr.arpa name = FQDN.
>
>
> I only get the FQDN when I lookup my other DCs. When I found this, I tried to use Samba-Tool to delete the hostname. record, but I get message that the record doesn't exist. If I then run samba-tool dns serverinfo hostname, I get the following error...
>
>
> ERROR(runtime): uncaught exception - (-1073741643, 'NT_STATUS_IO_TIMEOUT') File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run
>
> return self.run(*args, **kwargs)
>
> File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 703, in run
>
> dns_conn = dns_connect(server, self.lp, self.creds)
>
> File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 37, in dns_connect
>
> dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
>
>
> I then tried checking the sam.ldb to see how the record is entered using ldbedit --url=sam.ldb. When I look at it's record, there are at least 10 additional servicePrincipalName lines that are pointing to an old orphaned DC that I had to manually remove using ADSI and AD Sites and Services several months back. They are somehow attached to the Primary DC record in sam.ldb now. Could this be causing the DNS failure? If so, what if I were to take each DC down (over a weekend of course) then manually edit the record in sam.ldb on each DC making sure that only the one being edited was up at a time, then once all of the changes are complete bring each one back online. The database record would be the same on all DCs and therefore replication wouldn't cause any further damage.
>
Is there any chance you could post the record that you want to alter
> ??
>
> Recently one of my Samba4 (4.2.0 Ver) Domain Controllers started acting up. Authentication against it would time out and fail, but until recently the internal DNS was still working. Now the internal DNS fails. If I use nslookup and set the server to it, then look up any hostname I get "connection timed out; no servers could be reached". This DC is my primary and has all FSMO roles. I need to get this working again in order to seize those roles on one of my other DCs. During troubleshooting here are some of the things I found.
>
>
> If I nslookup the IP address of my primary DC on one of my other servers, I get two records
>
>
> 25.2.xxx.xx.in-addr.arpa name = hostname.
>
> 25.2.xxx.xx.in-addr.arpa name = FQDN.
>
>
> I only get the FQDN when I lookup my other DCs. When I found this, I tried to use Samba-Tool to delete the hostname. record, but I get message that the record doesn't exist. If I then run samba-tool dns serverinfo hostname, I get the following error...
>
>
> ERROR(runtime): uncaught exception - (-1073741643, 'NT_STATUS_IO_TIMEOUT') File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run
>
> return self.run(*args, **kwargs)
>
> File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 703, in run
>
> dns_conn = dns_connect(server, self.lp, self.creds)
>
> File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/dns.py", line 37, in dns_connect
>
> dns_conn = dnsserver.dnsserver(binding_str, lp, creds)
>
>
> I then tried checking the sam.ldb to see how the record is entered using ldbedit --url=sam.ldb. When I look at it's record, there are at least 10 additional servicePrincipalName lines that are pointing to an old orphaned DC that I had to manually remove using ADSI and AD Sites and Services several months back. They are somehow attached to the Primary DC record in sam.ldb now. Could this be causing the DNS failure? If so, what if I were to take each DC down (over a weekend of course) then manually edit the record in sam.ldb on each DC making sure that only the one being edited was up at a time, then once all of the changes are complete bring each one back online. The database record would be the same on all DCs and therefore replication wouldn't cause any further damage.
>
(suitably sanitized) ? It may be easier to just change the record on the
first DC and then let replication change the others.
Rowland
Donaldson Jeff
Nov 3, 2014, 12:30:03 PM11/3/14
to
Thank you. Below is the cleaned up record from sam.ldb. Any help is appreciated.
# record 752
dn: CN=PRIMARYDC,OU=Domain Controllers,DC=domain
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
objectClass: computer
cn: PRIMARYDC
instanceType: 4
whenCreated: 20130724141655.0Z
uSNCreated: 3583
name: PRIMARYDC
objectGUID: 83003f9f-ed01-4805-9bc2-162ac0216db0
userAccountControl: 532480
badPwdCount: 0
codePage: 0
countryCode: 0
badPasswordTime: 0
lastLogoff: 0
lastLogon: 0
localPolicyFlags: 0
pwdLastSet: 130191490150000000
primaryGroupID: 516
objectSid: S-1-5-21-276688905-1455118844-2751846679-67110187
accountExpires: 9223372036854775807
logonCount: 0
sAMAccountName: PRIMARYDC$
sAMAccountType: 805306369
operatingSystem: Samba
operatingSystemVersion: 4.2.0pre1-GIT-b505111
dNSHostName: primarydc
objectCategory: CN=Computer,CN=Schema,CN=Configuration,DC=domain
isCriticalSystemObject: TRUE
rIDSetReferences: CN=RID Set,CN=PRIMARYDC,OU=Domain Controllers,DC=domain
serverReferenceBL: CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=domain
msDS-SupportedEncryptionTypes: 31
whenChanged: 20130825181055.0Z
uSNChanged: 21555
servicePrincipalName: HOST/primarydc.domain
servicePrincipalName: HOST/primarydc.domain/NEWARKCHARTER
servicePrincipalName: ldap/primarydc.domain/NEWARKCHARTER
servicePrincipalName: GC/primarydc.domain/domain
servicePrincipalName: ldap/primarydc.domain
servicePrincipalName: HOST/primarydc.domain/domain
servicePrincipalName: ldap/primarydc.domain/domain
servicePrincipalName: HOST/PRIMARYDC
servicePrincipalName: E3514235-4B06-11D1-AB04-00C04FC2DCD2/0bd99af6-a59f-4143-
a56d-dae3dd6c2fd5/domain
servicePrincipalName: ldap/0bd99af6-a59f-4143-a56d-dae3dd6c2fd5._msdcs.domain
servicePrincipalName: ldap/PRIMARYDC
servicePrincipalName: RestrictedKrbHost/PRIMARYDC
servicePrincipalName: RestrictedKrbHost/primarydc.domain
servicePrincipalName: ldap/primarydc.domain/DomainDnsZones.domain
servicePrincipalName: ldap/primarydc.domain/ForestDnsZones.domain
servicePrincipalName: HOST/ORPHANDC.domain
servicePrincipalName: HOST/ORPHANDC.domain/NEWARKCHARTER
servicePrincipalName: ldap/ORPHANDC.domain/NEWARKCHARTER
servicePrincipalName: GC/ORPHANDC.domain/domain
servicePrincipalName: ldap/ORPHANDC.domain
servicePrincipalName: HOST/ORPHANDC.domain/domain
servicePrincipalName: ldap/ORPHANDC.domain/domain
servicePrincipalName: E3514235-4B06-11D1-AB04-00C04FC2DCD2/976c9c86-288d-483e-
baec-7043a9c4a6cd/domain
servicePrincipalName: ldap/976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.domain
servicePrincipalName: RestrictedKrbHost/ORPHANDC.domain
servicePrincipalName: ldap/ORPHANDC.domain/DomainDnsZones.domain
servicePrincipalName: ldap/ORPHANDC.domain/ForestDnsZones.domain
distinguishedName: CN=PRIMARYDC,OU=Domain Controllers,DC=domain
# record 753
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
________________________________________
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Rowland Penny <rowlan...@googlemail.com>
Sent: Saturday, November 1, 2014 7:54 AM
To: sa...@lists.samba.org
Subject: Re: [Samba] Non Functioning Internal DNS - Samba4
# record 752
dn: CN=PRIMARYDC,OU=Domain Controllers,DC=domain
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
objectClass: computer
cn: PRIMARYDC
instanceType: 4
whenCreated: 20130724141655.0Z
uSNCreated: 3583
name: PRIMARYDC
objectGUID: 83003f9f-ed01-4805-9bc2-162ac0216db0
userAccountControl: 532480
badPwdCount: 0
codePage: 0
countryCode: 0
badPasswordTime: 0
lastLogoff: 0
lastLogon: 0
localPolicyFlags: 0
pwdLastSet: 130191490150000000
primaryGroupID: 516
objectSid: S-1-5-21-276688905-1455118844-2751846679-67110187
accountExpires: 9223372036854775807
logonCount: 0
sAMAccountName: PRIMARYDC$
sAMAccountType: 805306369
operatingSystem: Samba
operatingSystemVersion: 4.2.0pre1-GIT-b505111
dNSHostName: primarydc
objectCategory: CN=Computer,CN=Schema,CN=Configuration,DC=domain
isCriticalSystemObject: TRUE
rIDSetReferences: CN=RID Set,CN=PRIMARYDC,OU=Domain Controllers,DC=domain
serverReferenceBL: CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=domain
msDS-SupportedEncryptionTypes: 31
whenChanged: 20130825181055.0Z
uSNChanged: 21555
servicePrincipalName: HOST/primarydc.domain
servicePrincipalName: HOST/primarydc.domain/NEWARKCHARTER
servicePrincipalName: ldap/primarydc.domain/NEWARKCHARTER
servicePrincipalName: GC/primarydc.domain/domain
servicePrincipalName: ldap/primarydc.domain
servicePrincipalName: HOST/primarydc.domain/domain
servicePrincipalName: ldap/primarydc.domain/domain
servicePrincipalName: HOST/PRIMARYDC
servicePrincipalName: E3514235-4B06-11D1-AB04-00C04FC2DCD2/0bd99af6-a59f-4143-
a56d-dae3dd6c2fd5/domain
servicePrincipalName: ldap/0bd99af6-a59f-4143-a56d-dae3dd6c2fd5._msdcs.domain
servicePrincipalName: ldap/PRIMARYDC
servicePrincipalName: RestrictedKrbHost/PRIMARYDC
servicePrincipalName: RestrictedKrbHost/primarydc.domain
servicePrincipalName: ldap/primarydc.domain/DomainDnsZones.domain
servicePrincipalName: ldap/primarydc.domain/ForestDnsZones.domain
servicePrincipalName: HOST/ORPHANDC.domain
servicePrincipalName: HOST/ORPHANDC.domain/NEWARKCHARTER
servicePrincipalName: ldap/ORPHANDC.domain/NEWARKCHARTER
servicePrincipalName: GC/ORPHANDC.domain/domain
servicePrincipalName: ldap/ORPHANDC.domain
servicePrincipalName: HOST/ORPHANDC.domain/domain
servicePrincipalName: ldap/ORPHANDC.domain/domain
servicePrincipalName: E3514235-4B06-11D1-AB04-00C04FC2DCD2/976c9c86-288d-483e-
baec-7043a9c4a6cd/domain
servicePrincipalName: ldap/976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.domain
servicePrincipalName: RestrictedKrbHost/ORPHANDC.domain
servicePrincipalName: ldap/ORPHANDC.domain/DomainDnsZones.domain
servicePrincipalName: ldap/ORPHANDC.domain/ForestDnsZones.domain
distinguishedName: CN=PRIMARYDC,OU=Domain Controllers,DC=domain
# record 753
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Rowland Penny <rowlan...@googlemail.com>
Sent: Saturday, November 1, 2014 7:54 AM
To: sa...@lists.samba.org
Subject: Re: [Samba] Non Functioning Internal DNS - Samba4
Rowland Penny
Nov 3, 2014, 1:00:03 PM11/3/14
to
this:
ldbedit -e nano -H /var/lib/samba/private/sam.ldb --cross-ncs -b
DC=primarydc,DC=example.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=example,DC=com
This should display your dns record
As for the no longer required SPN's, I would think that you should be
able to delete them without problems, but as usuall, make a a backup of
sam.ldb etc first, before you try anything.
Rowland
Donaldson Jeff
Nov 3, 2014, 4:30:06 PM11/3/14
to
Sorry, forgot to replay all...
Thanks! Here's the DNS record from your query...
# record 1
dn: DC=PRIMARYDC,DC=domain.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=domain,DC=com
objectClass: top
objectClass: dnsNode
instanceType: 4
whenCreated: 20130724141714.0Z
uSNCreated: 3656
showInAdvancedViewOnly: TRUE
name: primarydc
objectGUID: b119f8e2-64d8-4482-b6b1-9dc9388950a4
objectCategory: CN=Dns-Node,CN=Schema,CN=Configuration,DC=domain,DC=com
dc: primarydc
dnsRecord:: BAABAAXwAABuAAAAAAADhAAAAAAAAAAACrMCGQ==
whenChanged: 20131002220652.0Z
uSNChanged: 83735
distinguishedName: DC=primarydc,DC=domain.com,CN=MicrosoftDNS,DC=DomainDnsZ
ones,DC=domain,DC=com
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
________________________________________
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Rowland Penny <rowlan...@googlemail.com>
Sent: Monday, November 3, 2014 12:51 PM
Thanks! Here's the DNS record from your query...
# record 1
dn: DC=PRIMARYDC,DC=domain.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=domain,DC=com
objectClass: top
objectClass: dnsNode
instanceType: 4
whenCreated: 20130724141714.0Z
uSNCreated: 3656
showInAdvancedViewOnly: TRUE
name: primarydc
objectGUID: b119f8e2-64d8-4482-b6b1-9dc9388950a4
objectCategory: CN=Dns-Node,CN=Schema,CN=Configuration,DC=domain,DC=com
dc: primarydc
dnsRecord:: BAABAAXwAABuAAAAAAADhAAAAAAAAAAACrMCGQ==
whenChanged: 20131002220652.0Z
uSNChanged: 83735
distinguishedName: DC=primarydc,DC=domain.com,CN=MicrosoftDNS,DC=DomainDnsZ
ones,DC=domain,DC=com
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
________________________________________
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Rowland Penny <rowlan...@googlemail.com>
Rowland Penny
Nov 3, 2014, 5:30:03 PM11/3/14
to
differences) , only thing I noticed is, you initially created the record
on the 24th July 2013 and it was changed on the 2nd Oct 2013, do these
date mean anything to you ?
Donaldson Jeff
Nov 3, 2014, 6:50:03 PM11/3/14
to
The July date was when we first moved from Samba3 to 4. Not sure about the October date. Any ideas on what other things I can/should look at? Thanks!
Donaldson Jeff
Nov 6, 2014, 11:00:04 AM11/6/14
to
Update - last night I stopped Samba services on my PrimaryDC. I created a backup of the private directory. I then manually edited the sam.ldb and removed the odd servicePrincipalNames from orphaned DC on the PrimaryDCs record. Samba services started without issues and DNS started working. After a little while, it would intermittently stop and start working again. Even when DNS wasn't working, I could still run the DNS tests and get the correct results with...
host -t SRV _ldap._tcp.domain.com
host -t SRV _kerberos._udp.domain.com
host -t A primaryDC.domain.com
host -t CNAME primarydcguid._msdcs.domain.com
I also saw the same behavior when running samba-tool drs showrepl. Randomly it would work, then fail. Interestingly though, the samba-tool drs kcc -Uadministrator primaryDC.domain.com failed every time with the following error...
Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2@ncacn_ip_tcp:primarydc.domain.com[1024,seal] NT_STATUS_IO_TIMEOUT
ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to primarydc.domain.com failed - drsException: DRS connection to ncssamba1.ncs.k12.de.us failed: (-1073741643, 'NT_STATUS_IO_TIMEOUT')
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect
(ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions) = drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds)
File "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", line 54, in drsuapi_connect
raise drsException("DRS connection to %s failed: %s" % (server, e))
This morning DNS stopped working again, even with a samba service restart. I'm not sure where to go from here. Any help is appreciated.
Regards,
Jeff
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
________________________________________
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Donaldson Jeff <Jeff.Do...@ncs.k12.de.us>
Sent: Monday, November 3, 2014 6:25 PM
To: Rowland Penny
Cc: sa...@lists.samba.org; O'Neill James; David Hopkins
host -t SRV _ldap._tcp.domain.com
host -t SRV _kerberos._udp.domain.com
host -t A primaryDC.domain.com
host -t CNAME primarydcguid._msdcs.domain.com
I also saw the same behavior when running samba-tool drs showrepl. Randomly it would work, then fail. Interestingly though, the samba-tool drs kcc -Uadministrator primaryDC.domain.com failed every time with the following error...
Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for e3514235-4b06-11d1-ab04-00c04fc2dcd2@ncacn_ip_tcp:primarydc.domain.com[1024,seal] NT_STATUS_IO_TIMEOUT
ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to primarydc.domain.com failed - drsException: DRS connection to ncssamba1.ncs.k12.de.us failed: (-1073741643, 'NT_STATUS_IO_TIMEOUT')
File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", line 39, in drsuapi_connect
(ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions) = drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds)
File "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", line 54, in drsuapi_connect
raise drsException("DRS connection to %s failed: %s" % (server, e))
This morning DNS stopped working again, even with a samba service restart. I'm not sure where to go from here. Any help is appreciated.
Regards,
Jeff
Jeff Donaldson
Technology Director
Newark Charter School
jeff.do...@ncs.k12.de.us
(302) 369-2001 ext: 425
From: samba-...@lists.samba.org <samba-...@lists.samba.org> on behalf of Donaldson Jeff <Jeff.Do...@ncs.k12.de.us>
Sent: Monday, November 3, 2014 6:25 PM
To: Rowland Penny
Cc: sa...@lists.samba.org; O'Neill James; David Hopkins
0 new messages