Windows Server 2003 - forward lookup zones

My shiny new Windows server has something odd going on in DNS forward lookup.

Our old 2000 server had standard domain.com forward lookups, and I put pointers in to allow client machines to see our website and for FTP to it and so on.

For reasons unknown (to me) I've ended up with three lots of forward lookups, listed under:

_msdcs.domain.domain.com

domain.domain.com

domain.com

So, I was trying to add the relevant pointers into domain.com forward lookup for our website IP address and I can't. It throws out an error that the "associated pointer record cannot be created, probably because the referenced reverse looup zone cannot be found".

So, I need to know:

1. Can I (or should I) safely get rid of the first two lookup groups, _msdcs.domain.domain.com and domain.domain.com respectively without causing mayhem ?

How can I get the relevant records added to our domain.com forward lookup to allow web and FTP access to our hosted domain without that error ?
CopyleftAsked:
Who is Participating?
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

> How can I get the relevant records added to our domain.com forward lookup to allow web
> and FTP access to our hosted domain without that error ?

Add a Host (A) Record to domain.com called www, or ftp, or any other name used and tell it the IP Address of your Web Server.

Untick the box that says to create the PTR (Pointer) Record, if it's a Public IP then you don't want a Reverse Lookup Zone for that.

Chris
0
 
chikenheadCommented:
if you delete
_msdcs.domain.domain.com

you will most likely prevent users from logging on to your network..  

This zone file has all the SRV records for your forest, and should be replicating with a forest scope.

The other two should represent two domains that exist in your AD environment.  

0
 
DrDave242Commented:
Is there anything in the two "extra" zones besides NS and SOA records?  If not, they're not performing any function, and you can get rid of them.  If they actually contain other records, you'll need to figure out why and if they're actually being used by anything before you toss them.

Also, is there a folder called _msdcs inside your domain.com forward lookup zone?  There really should be, and it should contain a fairly large tree of folders of SRV records.  If it's missing entirely, you'll need to create it.  I'd wager that it's there, though, or you'd be having other problems.
0
 
CopyleftAuthor Commented:
Many thanks.

It was the bit where you said "Untick the box that says to create the PTR (Pointer) Record, if it's a Public IP then you don't want a Reverse Lookup Zone for that" that did it.

I hate to say the words and invite the inevitable chaos that will likely follow, but everything seems to be ticking along very nicely now ;o)

Thanks again.
0
All Courses

From novice to tech pro — start learning today.