Bug 9750 - Cannot Delete MX Records when compiled on 32-bit Linux
Summary: Cannot Delete MX Records when compiled on 32-bit Linux
Status: NEW
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: DNS server (show other bugs)
Version: unspecified
Hardware: x86 Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Kai Blin
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-29 10:06 UTC by Thomas Simmons
Modified: 2013-03-29 10:10 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Simmons 2013-03-29 10:06:52 UTC 
I have duplicated this behavior on a clean install/compile/provision using CentOS 6.3, CentOS 6.4 and Ubuntu 12.04. This occurs with all versions of Samba 4 (4.00 - 4.0.4).

1) Provision domain
2) Create MX record (samba-tool or ADUC)
3) Attempt to delete MX record (samba-tool or ADUC)
Comment 1 Thomas Simmons 2013-03-29 10:07:51 UTC 
***Create MX Record OK:

 [root@ADC1 log]# samba-tool dns query adc1 internal.testdom.com mailsrv
 MX
 GENSEC backend 'gssapi_spnego' registered
 GENSEC backend 'gssapi_krb5' registered
 GENSEC backend 'gssapi_krb5_sasl' registered
 GENSEC backend 'sasl-DIGEST-MD5' registered
 GENSEC backend 'schannel' registered
 GENSEC backend 'spnego' registered
 GENSEC backend 'ntlmssp' registered
 GENSEC backend 'krb5' registered
 GENSEC backend 'fake_gssapi_krb5' registered
 Using binding ncacn_ip_tcp:adc1[,sign]
   Name=, Records=3, Children=0
     MX: mailsrv.internal.testdom.com. (10) (flags=f0, serial=4, ttl=900)

***Delete MX Record Fails:

 [root@ADC1 log]# samba-tool dns delete adc1 internal.testdom.com mailsrv
 MX 'mailsrv.internal.testdom.com 10'
 GENSEC backend 'gssapi_spnego' registered
 GENSEC backend 'gssapi_krb5' registered
 GENSEC backend 'gssapi_krb5_sasl' registered
 GENSEC backend 'sasl-DIGEST-MD5' registered
 GENSEC backend 'schannel' registered
 GENSEC backend 'spnego' registered
 GENSEC backend 'ntlmssp' registered
 GENSEC backend 'krb5' registered
 GENSEC backend 'fake_gssapi_krb5' registered
 Using binding ncacn_ip_tcp:adc1[,sign]
 ERROR(runtime): uncaught exception - (9701,
 'WERR_DNS_ERROR_RECORD_DOES_NOT_EXIST')
   File
 "/usr/local/samba/lib/python2.6/site-packages/samba/netcmd/__init__.py",
 line 175, in _run
     return self.run(*args, **kwargs)
   File
 "/usr/local/samba/lib/python2.6/site-packages/samba/netcmd/dns.py", line
 1169, in run
     del_rec_buf)
Comment 2 Thomas Simmons 2013-03-29 10:10:48 UTC 
Debug Output (log level = 10)

 [2013/03/20 13:52:20,  5, pid=2064, effective(0, 0), real(0, 0)]
 ../lib/ldb-samba/ldb_wrap.c:69(ldb_wrap_debug)
   ldb: ldb_trace_request: SEARCH
    dn:
 DC=internal.testdom.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=internal,DC=testdom,DC=com
    scope: one
    expr: (&(objectClass=dnsNode)(name=mailsrv))
    attr: dnsRecord
    control: <NONE>

 [2013/03/20 13:52:20,  5, pid=2064, effective(0, 0), real(0, 0)]
 ../lib/ldb-samba/ldb_wrap.c:69(ldb_wrap_debug)
   ldb: ldb_trace_request: (resolve_oids)->search

 ...
 ... TRIMMED REPEATED MESSAGES
 ...

 [2013/03/20 13:52:20,  5, pid=2064, effective(0, 0), real(0, 0)]
 ../lib/ldb-samba/ldb_wrap.c:69(ldb_wrap_debug)
   ldb: ldb_trace_response: ENTRY
   dn:
 DC=mailsrv,DC=internal.testdom.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=internal,DC=testdom,DC=com
   dnsRecord::
 IgAPAAXwAAAEAAAAAAADhAAAAAALIDcAAAoeBAdtYWlsc3J2CGludGVybmFsB7G4YX
    lzZXMDY29tAA==
   dnsRecord:: EAAPAAXwAAA+AAAAAAAAAAAAAADcIjcAAAoMAgZnb29nbGUDY29tAA==
   dnsRecord::
 IgAPAAXwAAAEAAAAAAADhAAAAAALIDcAAAoeBAdtYWlsc3J2CGludGVybmFsB7G4YX
    lzZXMDY29tAA==

 [2013/03/20 13:52:20,  5, pid=2064, effective(0, 0), real(0, 0)]
 ../lib/ldb-samba/ldb_wrap.c:69(ldb_wrap_debug)
   ldb: ldb_trace_response: DONE
   error: 0

 [2013/03/20 13:52:20,  1, pid=2064, effective(0, 0), real(0, 0)]
 ../librpc/ndr/ndr.c:282(ndr_print_function_debug)
        DnssrvUpdateRecord2: struct DnssrvUpdateRecord2
           out: struct DnssrvUpdateRecord2
               result                   :
 WERR_DNS_ERROR_RECORD_DOES_NOT_EXIST