DNS Best Practices

Discussion in 'Windows Server' started by Shaun, Sep 22, 2004.

  1. Shaun

    Shaun Guest

    Before we get started let me set the scene. My organization is currently a
    Windows NT enviroment but will soon be embarking on Active Directory 2003.
    We currently have a DMZ via one-arm routing. We have three web servers in
    this DMZ and all are isolated from the internal network. Currently our DNS
    is outsourced but we are looking to bring it in house do to some reliability
    issues we have been having with our vendor. I am thinking that it would be
    best to create a Windows 2003 DNS server in our DMZ for the web servers. On
    the internal network install DNS integrated with AD and have the internal
    DNS/AD servers foward request for addresses outside of the internal network
    to the DNS servers in the DMZ. We are looking at security and preventing
    things such as footprinting. I am on the right track here, or is my maddness
    flawed? Please advise
     
    Shaun, Sep 22, 2004
    #1

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. DNS Best Practices (guidance)

  2. Exchange, SBS and Reverse DNS - Best Practices??

  3. Best AD/DNS 2003 design practices for multiple international sites?

  4. Question re: DNS forwarding best practices

  5. Best practices Windows 2003 DNS in child domain

  6. dns best practices

  7. DNS best practices

Loading...