Dns soa serial reset

Steps 1 and 2 can be performed using the DNS serial number calculator provided in the tools section of this website. Serial numbers wrap around modulo 2 32 equal to To calculate the total distance you should therefore:. It is desirable that the number of steps be minimised in order to avoid unnecessary work.

This can be achieved as follows:. It is usually possible to reach the desired serial number in two steps. For the scenario considered here, those steps would be:. Each time the serial number is changed you must reload the zone into the master nameserver, then wait for it to propagate to all of the slaves.

You can check whether a zone change has propagated to a particular slave by requesting the SOA record for the zone:. The format of the answer is slightly different from the format used in a zone file, but it contains the same information including the serial number in the same order:. If you make a second change to the serial number when one of the slave nameservers has not registered the first one then instead of taking two steps forward the value will appear to have taken one step back.

If you open up your DNS management console and take a look at the Forward Lookup Zones node, it will list all your zones and whether they're AD-integrated or "normal" primary or secondary zones.

If you're actually running with primary and secondary zones, then your question makes sense and the answer would be to simply establish a new primary zone on another server and use the zone's text file on your current primary to populate the new DNS server with the current records. In terms of managing the process of replacing a domain controller with a new version built from scratch with a later operating system, then so long as you have other domain controllers already up and running the process is simple:.

What you'll find is that once the domain controller has finished the promotion process, which includes populating the DNS zone with data loaded from AD, you'll notice that the SOA record for the zone is that server.

Assuming you have more than one domain controller running DNS now, you can already see this behaviour through running the following command:. The final parameter instructs the nslookup command to query that specific server, and if you change the name from one domain controller to the next, you'll see that the SOA record returned as the result also changes to point to that domain controller. This is by design. However whatever be the case since you have Win DC and you need to upgrade win cross-platform upgrades x86 to x64 or vice-versa are not supported.

Also ensure that instances of the old DC is removed from DNS,AD sistes and service,DC OU and then during the non business hour demote the old server and change the hostname of new DC to old servername and change ip address as well if required.

You can use netdom command to change the DC name. Configure authorative time server on the PDC role holder server below is the KB article for the same. Hope this helps. Best Regards, Sandesh Dubey. Hi Everyone and thanks for the replies.

I realize I should have done a much better job explaining things so I'm going to try that now. We have three zones in our forward lookup zones, two are for external domains and one is for our actual AD domain.

The AD zone is setup as AD-Integrated the other two zones are not setup that way and are setup as primary-secondary zones. It sounds like from your response that I should be able to simply change the type of one of the secondary servers to primary. When I run that command and change the dns server to another dns server the lookup always returns the server that is currently set as the SOA.

Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Refresh Page. Sign in, instead. Email Address:. No, I am a new user :. Your Name:. Yes, I have a password. Forgot your password? Terms We respect your privacy Already have an account? Sign Up, instead. Terms We respect your privacy.