[cifs-protocol] [REG:110122106325012] strange records in DNS LDAP NCs

Bryan Burgin bburgin at microsoft.com
Mon Dec 20 23:00:30 MST 2010


Thx, Tridge.

I've seen the non-NULL dwReserved before and, as it turns out, I already have an inquiry on this.  As part of my follow-up to our IO Lab, I captured several DnsRecords to verify that dwTtlSeconds seemed to be in network order.  In the same report, I shared the observation that I was seeing dwReserved as non-NULL and parenthetically asked about it, too.

I saw notes that the PG discussed the issue I filed, but the outcome of that discussion was not available.  I'll ping the PG tomorrow.  However, finding folks this week is a bit of a challenge.  Is this blocking you?

Bryan

-----Original Message-----
From: tridge at samba.org [mailto:tridge at samba.org] 
Sent: Monday, December 20, 2010 6:30 PM
To: Bryan Burgin
Cc: cifs-protocol at samba.org; abartlet at samba.org; MSSolve Case Email
Subject: Re: [REG:110122106325012] strange records in DNS LDAP NCs

 > I created SR 110122106325012 to track this issue.  An engineer from the protocols team will contact you soon.

thanks. 

Here is an example of a non-zero dwReserved for the 2nd question:

dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0021 (33)
        wType                    : DNS_TYPE_SRV (33)
        dwFlags                  : 0x0000f005 (61445)
        dwSerial                 : 0x000002ac (684)
        dwTtlSeconds             : 0x00000258 (600)
        dwTimeStamp              : 0x00000000 (0)
        dwReserved               : 0x0036d5ee (3593710)
        data                     : union dnsRecordData(case 33)
        srv: struct dnsp_srv
            wPriority                : 0x0000 (0)
            wWeight                  : 0x0064 (100)
            wPort                    : 0x0185 (389)
            nameTarget               : w2k8r2b.v2.tridgell.net


 > 2) what is the dwReserved field in all the dnsNode records? The MS-DNSP doc says:
 > 
 >    dwReserved: This value MUST be set to 0x00000000 when sent by the client and ignored on
 >      receipt by the server.
 > 
 > but that makes no sense. These are fields that are sent by the LDAP or DRS server in response to queries. The values are far too consistent to be random. 
 > 
 > Note that we are not asking about the DNS RPC protocol that MS-DNSP concentrates on. In our case Samba is a DC that is replicating the DNS NCs with Microsoft DCs. We need to know how to fill in these fields when we create records that will be replicated to MS DNS servers via DRS.
 > 
 > Cheers, Tridge



More information about the cifs-protocol mailing list