Re: company.local or company.com

Your AD Servers in the office will most likely be the choice for DNS
resolution.

First issue: You will try and browse to company.com, however you will be
using internal AD DNS for resolution, not the external DNS servers that host
the external zone. This means you will have to add records into ADDNS when
adding records for the external zone.

Windows 2000 Server exam books have large chapters dedicated to this
namespace design (alternate good read here:
http://articles.techrepublic.com.com/5100-22_11-5098072.html), and Microsoft
themselves recommended not sharing internal and external namespaces.

Having your AD namespace called company.local will not affect anything as it
doesn't have to be externally routable, and won't conflict with any possible
external namespace you already have. It also won't affect Exchange as you
can configure your accepted domains and primary smtp address suffixes.

Go with the .local (unless you fancy the challenge of managing both
namespaces)

Oliver


.

Relevant Pages

  • Re: How is .local Used?
    ... have a good understanding of the relationship between the AD and FQDN ... namespace definitions and the implications associated with their setup. ... DNS for internal delivery using the .local namespace. ... > servers, workstations) should look to an AD integrated DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: Computer browsing, NETBIOS
    ... Perhaps what the "IT group" meant was to switch to using the DNS and WINS ... Name resolution and "Browsing" are separate things. ... that's what the Computer Browser service does. ... > Servers and WINS servers. ...
    (microsoft.public.win2000.networking)
  • Re: DNS Error after running DCPROMO
    ... point the new domain controller to itself for name resolution, ... whith a default DNS installation. ... > three new servers to the new domain, the message given is: ... when I open DNs admin on the DC, ...
    (microsoft.public.windows.server.dns)
  • Re: 2 sites - vpn link - Slow local browsing
    ... > Does name resolution occur the same way at both sites? ... Do i need wins on the servers? ... domaincontroller and secondary dns on the sec.domaincontroller. ... do i need to install winsservers for this ...
    (microsoft.public.windows.server.networking)
  • Re: Disaster recovery scenerios for DNS/AD
    ... > scenario then would probably be best to bring up a 3rd server with DNS ... > Primary and Alternate servers that already exist. ... > But for a short-time this caused issues and no resolution occurred. ... >> secondary zone and enable zone transfers. ...
    (microsoft.public.windows.server.dns)