Re: Why would anybody use .LOCAL?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jack T. (71045.3122_No_Spam_Here_at_compuserve.com)
Date: 03/25/04 

Date: Thu, 25 Mar 2004 12:03:32 -0500

> 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.

Relevant Pages

  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)
  • RE: Server 2003 Network problems since IP address change
    ... Rightclick "My Computer", properties, Computer name or network identification, ... Is there any firewall running on client or server? ... Is the Primary DNS ... of zone WSW.local. ...
    (microsoft.public.windows.server.networking)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)