.local vs .com



I have recently installed a SBS 2003 and a 2003 DC created a new domain.
both servers list a name of servername.domainname.local not .com. .com was
what I meant to have but I have been told .local will appear if .com is not
specified. In the DNS zones on each DC the reverse lookup zones match
displaying the two subnets. The forward lookup zone on the SBS server has
_msdc, domainname.com and domainname.local. The forward lookup zone on the
2003 DC has only domainname.local. I am receiving messages that replication
can't occur basically because the zones/partition can't be transfered. I
have seen articles mentioning Creating a new partition under DNS forward
lookup zones and the option is available. A mail server in located inside
and remote users connect to it for webmail. Additionally, laptop users
report extremely slow connection speeds on the internal network. All PCs
were joined to domainname and I am not sure whether .com was specified. I
have a couple of questions first. Does it matter whether .com or .local is
used? Second, if I need to change the .local to .com, what is the process?
.



Relevant Pages

  • Re: DCDIAG DNS Failure
    ... Adding a ptr record for the loopback address in the reverse lookup zone. ... Having the DNS server point to the loopback address instead of hard ... I cleaned up the extra zones referring to the loopback address ... Without advance view I have 4 forward lookup zones and 7 ...
    (microsoft.public.windows.server.dns)
  • Re: reverse lookup zone records !!
    ... > lookup zones because we have for instance 3 or more ... > zones constantly duplicate host records associated to ip ... You can use the scavenging funtion in DNS. ... 301644 - DNS Server Forced Scavenge Does Not Immediately Start Zone ...
    (microsoft.public.win2000.dns)
  • Re: Reverse Lookup Zones - Multiple Subnets/Multiple DNS Servers
    ... > I am trying to figure out the best way to implement reverse lookup zones ... > multiple DNS servers. ... your REVERSE issues are unrelated to the above -- ...
    (microsoft.public.windows.server.dns)
  • Re: No Reverse Lookup
    ... The reverse lookup, however, do not work externally. ... In general, the Reverse lookup zones belong to the ISPs, ... you should not be to host either ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Mass Changes
    ... Also I'm concerned about the secondary servers updating. ... >> lookup zones that will change the SOA expire from ... >> inputting as new Forward Lookup Zones. ... > Win2k on the standard primary zones, if the zones are AD integrated they get ...
    (microsoft.public.windows.server.dns)