quote:

ORIGINAL: trw2006

now I understand the split dns.  TY       while implementing the instructions in this article i found some decrepancies that happened while i configed my sbs2003 server. 

When entering host A records for the internal side dns i noticed that checking the create pointer resulted in an error message stating i could not do it because i had no reverse lookup zone related to the new forward zone.  So I created them anyway w/o pointers. Is a rev zone needed here? Hmm I saw dozens of other posts elsewhere of stumped people too, not from ur article tho.

On the step where the new zone is created "forward" type was not mentioned but of course it was implied. Newbees like me need the all the details.  Thats not a biggy but not mentioning in the steps that under properties of the new zone, when created, "allow zone transfers" is checked by default and that could be bad as I read.  I only noticed it cuz i check over the properties on all this stuff and some folks arent so thorough.

4/5 stars on this and TY Tom for the great info.  I enjoy and appreciate all your articles.   TW

quote:

ORIGINAL: dglasgow

I am trying to implement Split DNS, but my problem is as follows. I have web sites hosted ON the ISA 2004 server. These sites are on a port different from 80 (they use 9999) and rely on host headers. When I implement the split dns, internal clients are not able to access the web sites because (I believe) the dns is pointing them to the IP, but not the correct port. Nslookup shows that internal clients are properly seeing the correct ip address for the fqdn. Any suggestions?

quote:


You can get a public DNS server. You can use a DDNS provider like TZO and register an external zone there.

quote:

ORIGINAL: PietjePuck

Great article, but I maybe have an addition, an important reason not to have a spit DNS zone is the hassle of managing the external hostnames especially when there are a lot of hostnames involved (like www, mail, ftp etc) and you only want to make a single hostname available through ISA. What I do: I create a new zone with a single host except the host is the zone-name (if I publish office.domain.com; I create a zone named office.doamin.com). This frees me of the burden of managing the external hostnames but gives me the pleasure of the same hostname for internal and external use.

quote:

ORIGINAL: altmantc

quote:

ORIGINAL: PietjePuck

Great article, but I maybe have an addition, an important reason not to have a spit DNS zone is the hassle of managing the external hostnames especially when there are a lot of hostnames involved (like www, mail, ftp etc) and you only want to make a single hostname available through ISA. What I do: I create a new zone with a single host except the host is the zone-name (if I publish office.domain.com; I create a zone named office.doamin.com). This frees me of the burden of managing the external hostnames but gives me the pleasure of the same hostname for internal and external use.

Could you please give a short example on setting this up?  I'm in the process of setting up a SBS and I'm trying to decide how to setup the Active Directory domain name, etc.  I'd really like to try to get it setup this way if possible.  Could I make the active directory name domain.com or would the server's active directory name need to be office.domain.com?  Then what would I need to setup on the internal server and on the public DNS server? (i.e. how do I go about setting up the office.domain.com entries)

quote:

ORIGINAL: rrao

Love the article. But I have a slightly different setup than what you've used. I am currently using the firewall that is provided by SBS 2003, instead of ISA. Given this setup and following the instructions on setting up the split-dns, I am only able to view the default page on the SBS server default website. The website that I am trying to access from the internet sits on a seperate Win 2003 server on the intranet, with the internal dns pointing to it with an A record.

I've opened up the firewall to allow access to the whole web site, but it still returns the default page. I can view the website on the intranet. Please let me know what I need to do to resolve this issue. I have a firewall router interfacing with the internet and the SBS server sits behind it.

Rahul.