Re: SBS self hosting DNS setup
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Wed, 15 Feb 2006 12:30:02 -0500
In news:321A0B4D-E2B7-49D3-8600-83A5F0CB4A47@xxxxxxxxxxxxx,
TheDude(Tom) <TheDudeTom@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I
commented on below:
Thks Ace. I closed other post. I thought I made this question clear
by stating I created a a new FW LUP zone for mycomp.com for external
access to my intranet.
I make the owa, www etc entries at the public DNS provider to point
to my outside router IP. But what entries go in the new mycomp.com
zone? where do they point? 10.x.x.2 or 68.x.x.46, internal nic ?
Yes, for internal users, the internal NIC only.
I created mail.mycomp.com in public dns. Don't I need a matching
record for mail, www, owa etc on my internal dns? My internal mail
server's name is stevie not mail. So do I have this wrong?
Internal machines, assuming they are using Exchange and Outlook, do NOT
require a 'mail' or MX record.
I thought the split dns is the solution to mixing up the dns records.
And prevents looping back.
No. It's just to make the logon names the same as their email addresses. It
complicates matters if you ask me. Also, if the webserver is hosted
elsewhere, or even internally on a different server other than the DCs (in
your case your sole SBS), don't expect to get to it by not using the 'www'
in front of the domain name. If you want to do that, there are more steps
involved.
Also, you've got an issue with the multihomed DC. Multihoming a DC is not
recommended and there are NUMEROUS steps to fix it and ensure AD
functionality and that the DNS SRV registration records for AD are correct.
Why is there no comprehensive MS article/how to for this on SBS? All
i can find are bits and pieces. Nobody self hosts?
Yes, many self host. However, this is an industry thing based on scenario
and not Microsoft specific when it comes to internal/external domains the
same and using private/public (NAT) IPs.
" If you are attempting to host your external domain on your internal
DNS,
then there's an issue with mixing private IPs and public IPs. YouWhy did you say this? It's blatently obvious.
just can't do it. You'll need a separated DNS server just for the
public records. Matter of fact, the registrars want you to have a
minimum of two DNS servers for each domain zone."
So is this:
If you want to offer your users OWA, OMA, FTP, WWW, those records
must be
made on the DNS server(s) hosting your public zone and all pointing
to that
68.x.x.46 address. You can't do this internally and expect the
internal clients to connect to the outside IP and be redirected back
in. NAT doesn't work that way, no matter from what manufaturer.
By my mentioning Split dns both of these issues are moot. Can you
please be more specific?
Is there a preferred Microsoft way to set this up? Tom
There is no "Microsoft" specific way of doing any of these other than what's
been practiced in teh industry by many, and depends on your scenario. I
mentioned the above stuff as a 'just-in-case' since many people when they
post DO NOT GIVE all the pertenent info about their scenario and many of us
need to guess, assume or ask questions.
If you say they're moot, then I assume you understand the issues with NAT.
NAT won't do a U-Turn from an internal request to it's outside IP back
internally whether using a Microsoft NAT solution or ANY OTHER name brand
(Cisco, Netscreen, Linksys, Netgear, etc etc etc). It's a NAT limitation.
That is why you need to create your internal records if accessing an
internal resource that you *may* be hosting externally with an iternal
private IP. As for Exchange and Outlook, that is a MAPI connection using AD
resources to authenticate and access the mail server. If you were to be
using POP or IMAP internally, then you would need to specifically stipulate
the internal private IPs.
Does that make sense? Please elaborate on anything that doesn't.
Ace
.
- References:
- Re: SBS self hosting DNS setup
- From: Ace Fekay [MVP]
- Re: SBS self hosting DNS setup
- From: TheDude(Tom)
- Re: SBS self hosting DNS setup
- Prev by Date: DNS - Active Directory Problems
- Next by Date: DNS issue on Exchange
- Previous by thread: Re: SBS self hosting DNS setup
- Next by thread: Re: Disabled NIC IP still resolves
- Index(es):
Relevant Pages
|
