You are incorrect on both counts.
I wrote at considerable length last week regarding the issues on the
client. They are a very big deal.
You're going to tell me this is a very big deal?
int DNS_Query(char *pszQuery,char *pszServer,unsigned short usPort,unsigned
short rr_type,char *achBufIn)
{
WSADATA stWSAData;
HEADER *pDNShdr;
unsigned short wWSAVersion=0x0101;
unsigned s;
struct sockaddr_in stSockAddr;
int nAddrLen=sizeof(struct sockaddr_in);
struct hostent *pHostEnt;
struct servent *pServEnt;
char achBufOut[BUFSIZE]={0};
char *p;
int nQueryLen,nRC,nWSAErr;
if (rr_type<17) // 17? Remove this limit entirely! What's the "ANY" type
code anyway?
p = DNS_RR_Type[rr_type];
else
p = "ANY";
[...]
switch (ntohs(q->rr_type)) {
[...]
case T_HYPOTHETICAL_MARID_TYPE:
[blah blah blah do stuff]
break;
[...]
...for an arbitrary record type code?
That's a code snippet from a really old Winsock DNS resolver I found
somewhere and adapted to query DMP records. I hacked bits of it as an
example of how to add MARID support.
Now if the DNS server answering this client can't forward a query for an
arbitrary record type, that's a server problem, alright. But the client is
trivial.
And, prompted by your mail, I just went and double checked the server
issue: the DNS server in Windows Server 2003 does NOT support
the syntax
of RFC 3597 or any other means to define instances of new RR types in
either its GUI editor or in its zone file text parser.
These are implementation issues only, and testing aside, this RFC just
doesn't seem so hard to code for. Expected in Win2K Service Pack 5, perhaps?
Or I could just swap out NTDNS with BIND 9 which supports Active Directory
and dynamic updates just fine, and support a MARID or other record type.
--
PGP key (0x0AFA039E):
<http://www.pan-am.ca/consulting(_at_)pan-am(_dot_)ca(_dot_)asc>
Sometimes it's hard to tell where the game ends and where reality bites,
er, begins. <http://vmyths.com/resource.cfm?id=50&page=1>