Dns windows 2003 problems

A colleague of mine discovered today that when he is logged onto the server "Server1" and he tries to connect to a network share using the DNS alias "Alias1", he cannot connect. This is now causing a major problem since we are running macros that have UNC's hard-coded in. Anyone know how to avoid this or have any quick fixes?

We could go in and change the UNC for the macros, but just wanted to throw this question out there to see if anyone experienced the same problems. Share Flag. All Answers. Collapse -. So I set the scavening to 5 days also. I will watch it and see. I did look at the timestamp and there are some fro So I am not sure what is going on, but I will wait a little while before I do anything drastic,.

Have you by any chance had another server running DHCP at some point in the past? The solution to this is to set any DHCP servers that you have to use a specific user account to register DNS records, that way if one server gets removed any other DHCP servers can still update the old records. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Thanks, Scott.

There have been a couple that could apply in this situation. There may have been more than just these two. Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 10 months ago. Active 9 years, 10 months ago. Viewed times. Can anyone seen this before or help please? To do this, run the following command:. If the resolver returns the IP address of a root server, you probably have a broken delegation between the root server and the name or IP address that you're trying to resolve.

Follow the Test a broken delegation procedure to determine where you have a broken delegation. If the resolver returns a "Request to server timed out" response, check whether the root hints point to functioning root servers.

To do this, use the To view the current root hints procedure. If the root hints do point to functioning root servers, you might have a network problem, or the server might use an advanced firewall configuration that prevents the resolver from querying the server, as described in the Check DNS server problems section.

It's also possible that the recursive time-out default is too short. Begin the tests in the following procedure by querying a valid root server. The test takes you through a process of querying all the DNS servers from the root down to the server that you're testing for a broken delegation. Resource record type is the type of resource record that you were querying for in your original query, and FQDN is the FQDN for which you were querying terminated by a period.

If the response includes a list of "NS" and "A" resource records for delegated servers, repeat step 1 for each server and use the IP address from the "A" resource records as the server IP address. If the response does not contain an "NS" resource record, you have a broken delegation.

If the response contains "NS" resource records, but no "A" resource records, enter set recursion , and query individually for "A" resource records of servers that are listed in the "NS" records. If you do not find at least one valid IP address of an "A" resource record for each NS resource record in a zone, you have a broken delegation. If you determine that you have a broken delegation, fix it by adding or updating an "A" resource record in the parent zone by using a valid IP address for a correct DNS server for the delegated zone.

If root hints appear to be configured correctly, verify that the DNS server that's used in a failed name resolution can ping the root servers by IP address.

If the root servers do not respond to pinging by IP address, the IP addresses for the root servers might have changed. However, it's uncommon to see a reconfiguration of root servers. If the server restricts zone transfers to a list of servers, such as those listed on the Name Servers tab of the zone properties, make sure that the secondary server is on that list. Make sure that the server is configured to send zone transfers.