DNS reinstall

[DanaK]

I need to know if there is anything that needs to be
manually deleted when DNS is uninstalled on a Domain
Controller. I had to back up and start over on a DC so I
uninstalled DNS and also demoted and then repromoted the
server using DCPROMO. I was looking through the DNS
subfolder under the system32 folder and found in the
Backup folder that the old domain name and address were
still in the backup files there. I've had some problems
getting the DNS to work and I was trying to determine if
there was anything that I should have manually deleted
when I got rid of the old domain.

The DNS recursive test under properties always fails but
the simple test always comes up passing. Also I tried to
install Symantec's Web Security today and it said there
was a problem with the DNS server. Of course it didn't
say exactly WHAT the problem was. It could be that the
name resolution on external addresses and names doesn't
work while internal names are resolved. Something's
missing but I don't know what.

 

[TIM ROBERTS]

Hi Dana,

You could make sure that this folder is gone %rootDrive%\WINNT\system32\dns
is gone once you remove DNS. If not you can remove it When install DNS it
will put this information back for you.
What knd of problems where you having? Where ther DNS errors in the event
logs? Can you do a nslookup to your domain name or if you perfer a dnscmd
commands?
Did you run netdiag / fix and then run netdiag /v /l produce a
netdiaglog.txt file, this might tells us some thing.
How many DNS server do you have? Is the zone AD intergrated? Does the DNS
server poin to itself for dns? Did you have forwarders configured? What
server pack are you at?

 

[Michael Johnston [MSFT]]

Make sure that the DC only points to it's internal IP for DNS. We don't want the ISP's DNS servers on either of the NICs. Then in DNS, on the Interfaces tab,
make sure you choose the option for Listen on: Only the follow addresses and make sure that the internal IP address is the only one listed. This will keep the
external interface from registering in the DNS zone. Be sure to disable the microsoft client and file and printer sharing on the external interface as well as
diable Netbios over TCP/IP.

Lastly, make sure the AD DNS zone is configured to allow dynamic updates. With all that setup, at a command prompt run "ipconfig/flush dns" then "ipconfig
/registerdns" and then restart the Netlogon service. Check the AD DNS zone to make sure it includes the SRV records for the AD. Check the A records for the
DC to make sure that the external IP address isn't listed. That should do it.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[DanaK]

All of what you suggested has been checked out and it is
set accordingly with the exception of the last check. The
records listed in the DNS server are SOA, WINS, NS and
there is an A record listed with the <server name> as well
as one that says "(same as parent folder)" for the same IP
address. There are also A records for all workstations
currently accessing the network.

One change I did try to make was checking the "Update
associated pointer (PTR)record". When I checked this it
would not remain checked. The Apply button would not be
made available. On the proxy server the box next
to "Delete when record becomes stale" has been marked. I
don't recall marking this at all. It has a static IP
address.

-----Original Message-----
Make sure that the DC only points to it's internal IP for

DNS. We don't want the ISP's DNS servers on either of the
NICs. Then in DNS, on the Interfaces tab,

make sure you choose the option for Listen on: Only the

follow addresses and make sure that the internal IP
address is the only one listed. This will keep the

external interface from registering in the DNS zone. Be

sure to disable the microsoft client and file and printer
sharing on the external interface as well as

diable Netbios over TCP/IP.

Lastly, make sure the AD DNS zone is configured to allow

dynamic updates. With all that setup, at a command prompt
run "ipconfig/flush dns" then "ipconfig

/registerdns" and then restart the Netlogon service.

Check the AD DNS zone to make sure it includes the SRV
records for the AD. Check the A records for the

DC to make sure that the external IP address isn't listed. That should do it.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the terms specified at

http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from which they originated.