Comment configurer dns windows 2003 server

DNS does this by using records stored in its database. On the Internet DNS mainly stores records for public domain names and servers whereas in private networks it may store records for client computers, network servers and data pertaining to Active Directory. We will begin by setting up a cache-only DNS server and progress to creating a primary forward lookup zone, a reverse lookup zone, and finally some resource records.

At the end of this article we will have set up a DNS server capable of resolving internal and external host names to IP addresses and the reverse. Before installing and configuring DNS on our server we have to perform some preliminary tasks. The suffix will be used to fully-qualify the server name. To begin:.

Our LAN is on a This tells the server to use its own DNS server service for name resolution, rather than using a separate server. After filling out those fields , click the Advanced button. To do this:. When the Windows Components Wizard comes up, scroll down and highlight Networking Services and then click the Details button.

Note that, during the install, Windows may generate an error claiming that it could not find a file needed for DNS installation. The wizard should automatically find the file and allow you to select it. After that, the wizard should resume the install. After this, DNS should be successfully installed. As our DNS server was just installed it is not populated with anything.

The Forward Lookup Zones node stores zones that are used to map host names to IP addresses, whereas the Reverse Lookup Zones node stores zones that are used to map IP addresses to host names.

A cache-only DNS server contains no zones or resource records. Its only function is to cache answers to queries that it processes, that way if the server receives the same query again later, rather than go through the recursion process again to answer the query, the cache-only DNS server would just return the cached response, thereby saving time.

With its limited functionality, a cache-only DNS server is best suited for a small office environment or a small remote branch office. However, in a large enterprise where Active Directory is typically deployed, more features would be needed from a DNS server, such as the ability to store records for computers, servers and Active Directory.

The DNS server stores those records in a database, or a zone. That means in a merger or supply-chain scenario you must be sure the other company doesn't plan on changing their DNS infrastructure by decommissioning old name servers, deploying new ones, or changing the IP addresses of existing ones. If they do change their infrastructure and don't inform you of this, then your name server may suddenly find itself forwarding queries to non-existing name servers resulting in failed name queries and frustrated users flooding help desk with calls.

In that case, it might be better to create stub zones on your name servers for zones for which the other company's name servers are authoritative. That's because stub zones automatically update themselves with the current list of name servers in the zone while configuring forwarders is a process that has to be done manually. Same thing in a large enterprise that has a complex Active Directory forest--if you aren't sure that administrators in other divisions of your company are going to tell you in advance when they change their DNS infrastructures, don't implement conditional forwarding--use stub zones instead.

The second caveat concerning conditional forwarding is not to get to carried away implementing it. You might think you could improve name resolution for your users by adding dozens of forwarders for the most popular Internet sites they use for work purposes, but this might be a bad idea.

The reason is, when you have a long list of conditional forwarders configured, your name server has to go through the entire list until it either finds the domain requested or fails to find it, in which case standard forwarding is used if configured , after which root hints is tried and standard recursion employed. The result of this is that your name server has to perform extra processing to go through the forwarders list each time a query is received, and in addition to increasing the CPU load on your server this can also result in slower name resolution rather than faster due to the time it takes to process an especially long list.

And if the forwarder itself is also part of your own company's DNS infrastructure then be aware that the added load of receiving forwarded queries from other name servers and performing recursive queries to resolve them means your forwarders will experience especially heavy CPU utilization and may need to have their hardware beefed up considerably to handle it.

So if you do plan on using conditional forwarding, particularly within your own enterprise, be sure to use it only where it really makes a difference and use it sparingly. He has written more than a thousand articles and has authored or been series editor for over 50 books for Microsoft Press and other publishers. He currently runs an IT content development business in Winnipeg, Canada. Your email address will not be published. Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry.

Over 1,, fellow IT Pros are already on-board, don't be left out! TechGenix reaches millions of IT Professionals every month, and has set the standard for providing free technical content through its growing family of websites, empowering them with the answers and tools that are needed to set up, configure, maintain and enhance their networks.

Forwarders and Forwarding When a name server is queried in DNS, the way it responds depends on the type of query issued, which can be either iterative or recursive. Post Views: 5, Join Our Newsletter Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry. I understand that by submitting this form my personal information is subject to the TechGenix Privacy Policy. Everything works ok so far.

But when i try to add another Windows server to the new domain i get the message: The following error occurred when DNS was queried for the service location SRV resource record used to locate a domain controller for domain storage.

Share Flag. All Comments. Collapse -. This question was closed by the author 0 Votes. Back to Windows Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.

Track this discussion and email me when there are updates. Reset Post Submit Post.