Update DNS records

I have some Domain controllers in one domain, I have changed their IP addresses, but when I went to DNS console it shows the old A records with old IP addresses.
Is there any way other than manual way to update the records?

Thanks

Install it on the DCs and run from there. It does not require a reboot and is basically a file copy with some DLL registrations.

After installing, you will have to path over to the install folder under Program Files in a command prompt as the path will not take until a reboot.

replacing DNS server

I have a Server 2003 Domain Controller which is also our DNS server.

This server has been giving us problems for a couple months now. We are planning on retiring the server.

We have created a Virtual server that is going to replace this domain controller/dns server.

I am not too familiar with configuring a DNS server.

What are the main things I have to do to configure the new dns server ?

The new server will have a new IP address and Name
We have another DNS server in our disaster recovery site.

A point in the right direction and a couple words of wisdom would be a great help

ComputerTechie:

Here a great how to if you are going to use windows 2003 dns server

http://www.petri.co.il/install_and_configure_windows_2003_dns_server.htm

I’ll just provide some general concepts so you have an idea of what you will do. It’s nice that your old server is still up, that will make things easier.

First, you will want to add the new server to your current DNS infrastructure, the link CT posted is very good. Basically, you will be:

Installing DNS on the new server
Configuring your forward and reverse lookup zones, downloading the current info from your existing server
Allow zone transfers from your old server to your new one

After the new server has been successfully added, remember before removing the old one, your clients must have the ip address of your new DNS server! If the clients are configured statically, you will need to change their DNS entries to point to the new server, if you use DHCP, you will need to update the DNS’s that are handed out by DHCP.

Also, make sure your new server has allowed and is allowed to transfer to all your other DNS servers.

Good luck, if you need some specific advice or clarification, we’re here to help.

If your DNS Zones are AD integrated then you won’t have to do much. When you dcpromo the new server to join it to your current domain as a DC then you select the DNS to be integrated with AD which will make DNS replicate all settings over to the new server. In AD integrated zones you don’t have to worry about the primary and secondary zones and zone transfers.

What is wrong with my DNS Server?

Got a call from a customer today who reports exceptionally slow Internet and the inability to get to MOST sites. When they connect to the neighbors open wireless they have no problems. The DNS server (10.0.2.10) is assigned by the DHCP server (also 10.0.2.10), and the default gateway is 10.0.2.1 (a Cisco ASA connected to the Internet with a PPPoE DSL connection). The server is Windows 2003 Std R2. Its IP address is 10.0.2.10 /255.255.255.0 with a DGW of 10.0.2.1.

When I connect to the server I can see the DNS server listed as 127.0.0.1. I tried adding the opendns.com as forwarders, and that APPEARED to help intermittently, but there are still definite issues. I removed the forwarders at this time. When I do an nslookup it USUALLY times out, but sometimes returns correct information. Even just putting opendns numbers in for the DNS server doesnt seem to resolve the issue.

I can connect to the server without issues, but cannot do tracert or ping diagnostic tests because the Cisco is programmed to block them, inbound and outbound. i do not yet have access to change this.

This server is a DC that is clearly not set up right (its on the 10.0.2.0 network, but AD Sites shows all 3 DCs in the domain as being in the same site, despite having different networks.) Strangely, there arent tons of errors in the event log like I would expect to see. While clearly wrong, I dont THINK thats the issue, as its been working for quite a while (it stopped working Monday)

The users also report other DNS related weirdness, including some users being able to access some sites but not others, and some users being able to access sites others cant access. There is no filtering solution in place, they are all on the same subnet, and there are no special rules in the firewall that could account for this.

When I run an nslookup on a site like microsoft.com, and set the debug mode on I get the output shown in the code section. SERVERDOMAIN is the customer’s domain.

If I use microsoft.com. (with the period at the end) it seems to work perfectly. However, if I do a different domain (such as google.com) it fails, whether I append the . at the end or not.

Now, after using the . at the end it resolves correctly whether I put the . at the end or not.
Setting the timeout to 5 seconds didnt seem to resolve the issue. The network connection is business DSL, and shows plenty of available bandwidth.

HEADER:
opcode = QUERY, id = 9, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0

QUESTIONS:
microsoft.com.SERVERDOMAIN.local, type = A, class = IN
AUTHORITY RECORDS:
SERVERDOMAIN.local
ttl = 3600 (1 hour)
primary name server
responsible mail addr
serial
refresh
retry
expire
default TTL
———
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
*** Request to localhost timed out

The delegated msdcs folder does causes issues in 2008. If you search the posts here you will see once you delete the two zones and recreate them so the msdcs folder will fall under the domain.com folder you shouldn’t see these errors anymore.

If queries sent directly to external DNS servers are intermittently failing as well, there may very well be a connectivity issue somewhere on the network. Do you know if queries to the internal DNS server for internal addresses ever fail? The router obviously doesn’t come into play in that case, so if they’re failing as well, maybe there’s a bad switch somewhere or something of that sort.

DNS record update

I have 6 DCs, 2 in each site(in each subnet in the LAN) they are all DNS ADIntegrated zone.
I have a computer that is joined to the domain and belongs to site1(subnet1), I have renamed the computer, but only the DNS servers in site1(subnet1) that have updates its record.

the other DNS servers in other sites(other subnets) haven’t updated the record.

It’s been 8 hours since I renamed the computer.

any idea ?

Thanks

Since the zone is AD-integrated, its data is replicated among the servers as part of AD replication. Do you have intersite AD replication set to occur only during a certain time interval (after business hours, for example), or can it occur at any time of day? If it can occur at any time, you may want to make sure you don’t have something preventing replication from taking place. AD Sites and Services would be the first place to check, along with the event logs of your DCs.

That all seems pretty reasonable. Are all of those replicating properly? Errors will be reported in the Directory Service log.

DNS Scavenging Issues

I have taken over a network that has some DNS issues. Scavenging has not been active in over two years. I know that this needs to be setup on intervals to automatically run but the issue I am having is that this doesn’t seem to do anything about the old host A files that already exist for machines that are long gone. On average each server on this network has 3 to 4 host A files attached to its ip address. I am very new to DNS so I am not quite sure how to deal with this issue? I can clean up the servers easily enough because their number is limited but i have 4000 plus clients that makes it unrealistic to try to fix the issue completely by hand.

I am sure there is a quick and dirty way to take care of this and any help would be great! I may just not be using scavenging correctly?

If you’re not sure what each of the values represents and want to understand how it fits together you might find this useful from the MS networking team:

http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

Once it’s running Scavenging can be happily ignored, it just sits in the background and gets on with it.

I also have some scripts that can be used to report on the state of records in a zone and their associated time stamps. I wrote them to help evaluate the impact of enabling Scavenging on a zone. Would they be any use to you?