That's actually fairly common. DNS is required for Active Directory domain controllers in Server 2003, but WINS is only used for older NetBEUI clients. The use of NetBEUI is deprecated in most modern Windows networks, so a WINS server is rarely used.
WINS server works only at level of LAN and uses a list of IP addresses with corresponding names, it does not allow you to use domains. DNS is almost the same thing but it allows you to span the network in domains and work with them.
If you have Windows ME/9x and below systems, use WINS for a NETBIOS name resolution server as DNS does not resolve up NETBIOS.
The Internal DNS Server ONLY.
What is the difference between a preferred DNS server and an altenate DNS server?Read more: http://wiki.answers.com/What_is_the_difference_between_a_preferred_DNS_server_and_an_altenate_DNS_server#ixzz2LRd3ICed
authoritative dns server is server that has own databases that has name resolution for the clients that for resolve from name to ip address and for ip address to name. non-authorititative dns server is server that forward request of dns client to authoritative dns server for resolve.
It provides single lable name resolution just like WINS. It also supports IPv6 unlike WINS.
Windows Internet Naming Service. It was used with a WINS server in older MS networks for name resolution. Newer MS Server OSs are tightly integrated with DNS and don't require WINS. WINS and DNS can only used for name resolution in a client/server network, such as a Windows domain. A workgroup (peer-to-peer) network uses NetBIOS over TCP/IP for name resolution
Unbound - DNS Server - was created in 2007.
DNS doctoring enables an internal host on a LAN to receive the Private ip of an internal server as an answer from a DNS query when using a DNS server that is outside the LAN, such as on the internet. A static NAT translation must also exist to translate the public IP to the private IP. Without DNS doctoring, the external DNS server will reply with the public IP address of the host on the internal LAN.
Primary zoneWhen a zone that this DNS server hosts is a primary zone, the DNS server is the primary source for information about this zone, and it stores the master copy of zone data in a local file or in AD DS. When the zone is stored in a file, by default the primary zone file is named zone_name.dns and it is located in the %windir%\System32\Dns folder on the server.Secondary zoneWhen a zone that this DNS server hosts is a secondary zone, this DNS server is a secondary source for information about this zone. The zone at this server must be obtained from another remote DNS server computer that also hosts the zone. This DNS server must have network access to the remote DNS server that supplies this server with updated information about the zone. Because a secondary zone is merely a copy of a primary zone that is hosted on another server, it cannot be stored in AD DS.Stub zoneWhen a zone that this DNS server hosts is a stub zone, this DNS server is a source only for information about the authoritative name servers for this zone. The zone at this server must be obtained from another DNS server that hosts the zone. This DNS server must have network access to the remote DNS server to copy the authoritative name server information about the zone.You can use stub zones to:Keep delegated zone information current. By updating a stub zone for one of its child zones regularly, the DNS server that hosts both the parent zone and the stub zone will maintain a current list of authoritative DNS servers for the child zone.Improve name resolution. Stub zones enable a DNS server to perform recursion using the stub zone's list of name servers, without having to query the Internet or an internal root server for the DNS namespace.Simplify DNS administration. By using stub zones throughout your DNS infrastructure, you can distribute a list of the authoritative DNS servers for a zone without using secondary zones. However, stub zones do not serve the same purpose as secondary zones, and they are not an alternative for enhancing redundancy and load sharing.There are two lists of DNS servers involved in the loading and maintenance of a stub zone:The list of master servers from which the DNS server loads and updates a stub zone. A master server may be a primary or secondary DNS server for the zone. In both cases, it will have a complete list of the DNS servers for the zone.The list of the authoritative DNS servers for a zone. This list is contained in the stub zone using name server (NS) resource records.When a DNS server loads a stub zone, such as abc.xyz.com, it queries the master servers, which can be in different locations, for the necessary resource records of the authoritative servers for the zone abc.xyz.com. The list of master servers may contain a single server or multiple servers, and it can be changed anytime.
DNS Major role and Fine Grained password policies in GPO and RODC
Legacy operating systems continue to use NetBIOS for name resolution to find a domain controller; however it is recommended that you point all computers to the Windows 2000 or Windows Server 2003 DNS server for name resolution.