Re: Why would anybody use .LOCAL?
From: Kevin D. Goodknecht [MVP] (admin_at_nospam.LSAOL.COM)
Date: 03/25/04
- Next message: Thomas Lee: "Re: Why would anybody use .LOCAL?"
- Previous message: Jeff Cochran: "Re: Why would anybody use .LOCAL?"
- In reply to: Jack T.: "Re: Why would anybody use .LOCAL?"
- Next in thread: Jack T.: "Re: Why would anybody use .LOCAL?"
- Reply: Jack T.: "Re: Why would anybody use .LOCAL?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 11:40:51 -0600
In news:O80kjsoEEHA.2272@TK2MSFTNGP09.phx.gbl,
Jack T. <71045.3122_No_Spam_Here@compuserve.com> posted a question
Then Kevin replied below:
>> To lower administration, if you use .LOCAL you don't have to worry
>> about
> setting up a split namespace to fix the conflicting authoritative DNS
> servers using the same name. The internal DNS just forwards the .com
> name.<
>
> Thanks Kevin. I must be missing something. If both the public and
> private DNS servers hosting the same zone are authoritative for the
> MyCompany.com zone, then:
> - The public DNS server will never see requests from the private
> network to resolve address for MyCompany.com resources because the
> private DNS will not forward for a domain that it is authoritative
> for. - The private DNS server will never see requests by the public
> network to resolve addresses for MyCompany.com resources because the
> public DNS server will never forward a for a domain that it is
> authoritative for.
>
> In the case where a resource is available both publicly and privately:
> - Either method requires making an entry in both the public and
> private DNS servers with a different address for each. One gets the
> public address of the router, and the other the private address of
> the SMTP server. - Using either method, there are two domains that
> are authoritative for the same resource.
> - Using the non-standard method, the user must be cognizant of network
> topology and his location. He must use .LOCAL if he is on the private
> network, either physically or via VPN, and .COM when his request is
> being routed through a public network. It also requires the
> additional administration of aliases to be setup for email users so
> that the .COM addresses are mapped to the .LOCAL domain. When
> someone sends and email to someone internally using MyCompany.COM,
> first the name is resolved externally where it gets the external
> address, which is the WAN interface. Then it is sent out the WAN
> interface, to the WAN interface. - Using the standard method, the
> user types in the same name no matter where he is located. No
> aliases need to be setup, and internal mail sent to .COM remains
> internal, since the local DNS server resolves the request to the
> private address of the SMTP server. The public DNS server never sees
> the resolution request nor does the WAN interface receive the
> traffic.
>
> What am I missing?
>
> Thanks,
> Jack T.
Since the internal DNS is authoritative over the internal mycompany.com zone
it won't forward so someone has to add the records to the internal DNS that
allow connection to public servers and sites under the name.
Hang around in here a while you'll be surprised about the number of posts "I
can't access our webiste, What can I do?" then they go on to say (At least
some do) "I am a DNS dummy" and some have no idea what you are saying when
you tell them to add a record named www to the internal zone with the IP of
the public website.
This problem does not arise if the name is .local because all .com names are
forwarded.
Any name you use doesn't keep you from adding a UPN logon name for
mycompany.com so users can logon with user@mycompany.com and adding
mycompany.com to exchange as an internal email address. All you have to do
is add it to the recipient policy and make it the default domain.
-- Best regards, Kevin D4 Dad Goodknecht Sr. [MVP] Hope This Helps ============================ -- When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. To respond directly to me remove the nospam. from my email. ========================================== http://www.lonestaramerica.com/ ========================================== Use Outlook Express?... Get OE_Quotefix: It will strip signature out and more http://home.in.tum.de/~jain/software/oe-quotefix/ ========================================== Keep a back up of your OE settings and folders with OEBackup: http://www.oehelp.com/OEBackup/Default.aspx ==========================================
- Next message: Thomas Lee: "Re: Why would anybody use .LOCAL?"
- Previous message: Jeff Cochran: "Re: Why would anybody use .LOCAL?"
- In reply to: Jack T.: "Re: Why would anybody use .LOCAL?"
- Next in thread: Jack T.: "Re: Why would anybody use .LOCAL?"
- Reply: Jack T.: "Re: Why would anybody use .LOCAL?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
