DNS Problem

Have Windows 2003 Server R2, Exchange 2003 Server, DNS and a DC all rolled
into one Server. All workstations, WinXP SP2, have the primary DNS pointing
to the DC (this is necessary for MS Outlook to access the Exchange Server).
The secondary DNS points to our ISP's DNS server (incase our DC goes down we
can still get to the internet). All workstations are registered in our DNS
in both Forward and Reverse zones. Our ISP's DNS servers are in our
Forwarders. We live on email and the internet.

Here is the problem:
We have a website hosted on the outside. It is the same name (ie., abc.com)
as our Lan domain name. When pinging our
domain name we get nothing. When using NSLOOKUP it points to our DC. Thus,
IE cannot go to our website. Is there
a way to solve our problem ?

Thanks,

Sam



.

Relevant Pages

  • Re: DNS Question
    ... If on my internal LAN I have workstations that are members of the ... External DNS resolution is done by the SBS, and those ISP DNS server IP ... Ethernet adapter Wireless Network Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: DCpromo issue. Health check on AD and group policy.
    ... We have also had intermittent issues with some workstations on the domain not ... The problem is I tryed to DCpromo this server yesterday and couldn't remove ... Single label AD DNS domain name. ... Otherwise, if you need additional specific assistance to get communication working, we'll need specific config info from your machines. ...
    (microsoft.public.windows.server.active_directory)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)