none
WWW host record necessary? RRS feed

  • Question

  • We have a single Windows 2008R2 DNS server.  Additionally, since we are a small church we only have a single forward lookup zone to support our private network.  The church does have 2 networks segregated at the router via 2 vlans (private and public vlans).  Our DHCP server is the router but our DNS server is a physical server that resides in the private vlan.  DNS services is disabled on the private vlan at the router so that the DNS resolution is done strictly by the physical DNS server on the private vlan.  The public network is a wireless public network that supports primarily guest services to the internet.

    We also have a web presence supported by an external Web company.  We do not have a web server or support any web hosting at the church.  It is all done by the web company we pay to support us.

    My question is this:  Since we do not host web servers or web hosting, why would we need a "www" host record?  Our last church adminstrator setup a "www" host record with IP address pointing to the primary web page that was created by the web company.  I don't understand why we would need this resource record.  Our web company hosts and establishes all our web pages.

    Thank you


    Cal Miyatake

    Thursday, June 30, 2016 8:40 PM

Answers

  • Hi;

    This was likely designed to help anyone who types in the "www" prefix into the web browser from inside your church.  As you said, your DNS resolution is done by the physical DNS server on the private plan, so any client on the private plan which is pointing to that DNS server for DNS resolution would use that www record as a pointer to the web server at your hosting company, which is likely listening on www.your_church.org as well as your_church.org.  I assume the DNS domain name on both sides is the same.



    Best Regards, Todd Heron | Active Directory Consultant

    Friday, July 1, 2016 12:50 AM
  • Hi,

    If you have an externally hosted website, but the internal domain name is the same as the external domain name, then you have what we call a Split-zone, or some call split-brain.

            In your zone, if the zone is NOT the same name as your Active Directory DNS domain name, then you can also create a blank record (right click, New, Host, leave the hostname blank, and simply type in the external IP.).

            If the zone is the SAME as your Active Directory DNS domain name,xxx.com will resolve to your DCs IP addresses and you should not add an empty A record to point to your website here as this will just create issues.

    In addition,if your external webstie is 'www.xxx.com',you could just type 'xxx' with 'Control+Enter' in address bar,it will complement with 'www' and 'com' automaticly.

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by Pearlyshells Wednesday, July 20, 2016 6:36 PM
    Friday, July 1, 2016 7:50 AM

All replies

  • Hi;

    This was likely designed to help anyone who types in the "www" prefix into the web browser from inside your church.  As you said, your DNS resolution is done by the physical DNS server on the private plan, so any client on the private plan which is pointing to that DNS server for DNS resolution would use that www record as a pointer to the web server at your hosting company, which is likely listening on www.your_church.org as well as your_church.org.  I assume the DNS domain name on both sides is the same.



    Best Regards, Todd Heron | Active Directory Consultant

    Friday, July 1, 2016 12:50 AM
  • Hi,

    If you have an externally hosted website, but the internal domain name is the same as the external domain name, then you have what we call a Split-zone, or some call split-brain.

            In your zone, if the zone is NOT the same name as your Active Directory DNS domain name, then you can also create a blank record (right click, New, Host, leave the hostname blank, and simply type in the external IP.).

            If the zone is the SAME as your Active Directory DNS domain name,xxx.com will resolve to your DCs IP addresses and you should not add an empty A record to point to your website here as this will just create issues.

    In addition,if your external webstie is 'www.xxx.com',you could just type 'xxx' with 'Control+Enter' in address bar,it will complement with 'www' and 'com' automaticly.

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by Pearlyshells Wednesday, July 20, 2016 6:36 PM
    Friday, July 1, 2016 7:50 AM
  • thanks for the info

    Cal Miyatake

    Wednesday, July 20, 2016 6:36 PM
  • Thanks for the info

    Cal Miyatake

    Wednesday, July 20, 2016 6:36 PM