<div>
It's done thru public IP address (your isp will provide to you) and a DNS register. You will also need to setup NAT's on your firewall to pass thru the public ip address's to your private network. <br />
<br />
Example:<br />
<br />
your domain is catco.com. Your ISP give's you a public ip address of 123.123.123.123. You register your domain name (catco.com) with a DNS register. You then setup a NAT on your firewall...123.123.123.123<wbr /> to pass thru your firewall to 10.x.x.x.(your private network). This is just a quick and dirty (I'm short on time). <br />
<br />
GL <br />
Kiba
</div>


It's done thru public IP address (your isp will provide to you) and a DNS register. You will also need to setup NAT's on your firewall to pass thru the public ip address's to your private network.

Example:

your domain is catco.com. Your ISP give's you a public ip address of 123.123.123.123. You register your domain name (catco.com) with a DNS register. You then setup a NAT on your firewall...123.123.123.123 to pass thru your firewall to 10.x.x.x.(your private network). This is just a quick and dirty (I'm short on time).

GL
Kiba

<div>
Thank you for the clarification... &nbsp;I was getting confused after reading some other posts. &nbsp;I don't host my own public records. &nbsp;I only NAT the public to private at the firewall for mail or www.<br />
<br />
<br />
<br />

</div>


Thank you for the clarification...  I was getting confused after reading some other posts.  I don't host my own public records.  I only NAT the public to private at the firewall for mail or www.





<div>
<div class="content wysiwyg-content">
I read to not expose your internal DNS service to the internet as this will expose information that shouldn't be public. &nbsp;Is this accomplished by using DNS Forwarders (ISP) and setting up your internal domain to use mydomain.local?
</div>
</div>


I read to not expose your internal DNS service to the internet as this will expose information that shouldn't be public.  Is this accomplished by using DNS Forwarders (ISP) and setting up your internal domain to use mydomain.local?

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.