Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
DNS Resolution with Windows Server 2008 R2 (with SP1)

Answered DNS Resolution with Windows Server 2008 R2 (with SP1)

  • Friday, May 25, 2012 2:19 PM
     
     
    Sign In to Vote
    0

    Hello.  In our environment we use split DNS.  Our internal DNS servers are using Windows Server 2008 R2 (with SP1).  Externally we use hosted solution by DNS Made Easy (www.dnsmadeeasy.com).

    A forward lookup zone (AD-Integrated) has been configured on our internal DNS servers (I will use "xyz.com" as my example - this is not our actual company).  I have created an A record for a server named wiki.xyz.com.  Also, the internal DNS server has been configured to use forwarders for queries it cannot resolve (specifically 8.8.8.8 and 8.8.4.4 which are Google's).

    Externally, I have created an A record for the same server (wiki.xyz.com) at our hosted DNS provider (DNS Made Easy).  This points to a public IP address which is NAT'd to our internal server.

    All the above configuration works fine.  My actual question is as follows:

    I create an external record named www.xyz.com which points to a hosted website provider.  This works fine for people accessing it from the public internet.  However, internally, I cannot resolve www.xyz.com using our internal DNS server which has the forwarders to Google DNS.

    If internal DNS cannot find www.xyz.com (which I know is not created internally), should DNS forward to Google DNS and find the record that is configured at DNS Made Easy?

    I know it works if I create the www.xyz.com internally, but I was wondering if I can avoid creating all these records internally?

    JP.

     

All Replies

  • Saturday, May 26, 2012 4:25 AM
     
     Answered
    Sign In to Vote
    0

    Hi,

    The query doesn't forward to Google DNS, if there is the DNS zone xyz.com to be hosted in the internal DNS. 

    To resolve the same record, the internal DNS also creates the A record in the DNS zone, xyz.com.

    You can also use the same name for the internal domain and the external domain. However, this method is not recommended. It creates name resolution problems because it introduces DNS names that are not unique. This method requires additional configuration to enable optimized performance.

    Reference:

    Creating Internal and External Domains

    http://technet.microsoft.com/en-us/library/cc755946(v=ws.10).aspx

    Regards, Terry | My Blog: http://terrytlslau.tls1.cc

    This posting is provided “AS IS” with no warranties, and confers no rights.

     
  • Tuesday, May 29, 2012 4:56 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thanks for posting here.

    Terry is right, we need to add a new A record “WWW” with pointing to the external IP address of our public web site on internal DNS server which is same as what we did previously to record “WIKI” .

    Thanks.

    Tiger Li

    Tiger Li

    TechNet Community Support