<div>
It is .. I am actually using variable to pass in a FQDN of a server which has an DNS A &nbsp;record but not a server record. &nbsp; But for some reason it is still sending out queries when I do a wireshark looking for a server record instead of just using the A record in DNS.<br />
<br />
Any suggestions.<br />

</div>


It is .. I am actually using variable to pass in a FQDN of a server which has an DNS A  record but not a server record.   But for some reason it is still sending out queries when I do a wireshark looking for a server record instead of just using the A record in DNS.

Any suggestions.


<div>
<div class="content wysiwyg-content">
Question: &nbsp;I am setting up a WSDL hitting a load balancer for our 2003 AD. &nbsp;I am curious if there is a way to force the LDAP bind using either SPSP or SDP to not look for the DNS Server record but instead only use the A record. &nbsp;2.0 NET is being used. &nbsp;<br />
<br />

</div>
</div>


Question:  I am setting up a WSDL hitting a load balancer for our 2003 AD.  I am curious if there is a way to force the LDAP bind using either SPSP or SDP to not look for the DNS Server record but instead only use the A record.  2.0 NET is being used.  



C# LDAP Bind how to bypass Server Record and use A record Directly

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.