B
Bob
I will be promoting a server to an Active Directory domain
controller and wonder what the best way to handle the
following scenario is.
I already have a FQDN with webhosting for the domain
handled externally, I will not be hosting the website on
my server. For the purposes of this discussion, I will
refer to this website domain as externaldomain.com.
My intention is to promote the server and set the domain
name to externaldomain.com. My concern is when systems on
this "internal" domain try to access the webserver or mail
server hosted externally. Will the DNS forwarder send the
request to the internet domain servers if it is unable to
find the "www" or "mail" machines in it's DNS records?
Will I have to add a DNS record to point the "www"
or "mail" requests to the internet web server or external
DNS servers? What will be the best way to handle this?
Thanks.
controller and wonder what the best way to handle the
following scenario is.
I already have a FQDN with webhosting for the domain
handled externally, I will not be hosting the website on
my server. For the purposes of this discussion, I will
refer to this website domain as externaldomain.com.
My intention is to promote the server and set the domain
name to externaldomain.com. My concern is when systems on
this "internal" domain try to access the webserver or mail
server hosted externally. Will the DNS forwarder send the
request to the internet domain servers if it is unable to
find the "www" or "mail" machines in it's DNS records?
Will I have to add a DNS record to point the "www"
or "mail" requests to the internet web server or external
DNS servers? What will be the best way to handle this?
Thanks.