I currently have Windows Server Standard Edition 2003. It is my DC and currently runs IIS, Exchange 2003, DNS, and a few other little things. This is what I'm running into. For example I have a website name www.domain1.com. My Domain name on my network is also domain1.com. So in my DNS settings I have a forward lookup of domain1.com. I now want to use this server as the dns server that updates my outside dns which run Bind 9. However since domain1.com exists inside and outside of my network this causes a problem with AD dnss look ups and external lookups since they have the same names. The internal dns has all the internal records which would resolve private ips which couldn't be transfer to the other outside dns servers since those ips would be usless to them. Isn't there a way I can have the server start using a different forward zone? So instead of domain1.com change it to domain1.local and then I can have a domain1.com that I can manage and update external server. Is there a guide to do this or is it simple?
bpippin 0 Newbie Poster
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.