Re: DNS Setup

Ok all that makes sense. Just to make sure I am understanding I listed my
scheme below...I have a single server that does it all for me. Small
Business of 6 users. ***What do you mean by the DNS Server should be set to
forward to the Gateway DNS? How do you accomplish this?***

Server
IP:192.168.10.1
SM: 255.255.255.0
G:192.168.10.254
DNS: 192.168.10.1

Router
IP:192.168.10.254
DNS: WAN DNS IP's

Workstation
IP:192.168.10.2-253
SM:255.255.255.0
G:192.168.10.254
DNS:192.168.10.1



"Herb Martin" wrote:


"Jamie" <Jamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4A75232C-7166-4166-A9D9-C6F0A262C4FE@xxxxxxxxxxxxxxxx
Thank you for any help in advance. I have a saying when it comes to a
computer network that DNS is the devil and it is probably because I just
don't grasp the concept completely. Here is my question.

DNS is the KEY -- not the devil. Practically all DC replication and client
authentication (and thus access to resources) problems are really DNS
based -- due to mistakes by the admins.

I have a Win 2000 server, router, and workstations. My server is setup to
be a DNS server but I don't think everything is working right. My first
questions are:

What should the DNS address on the server, router, and workstations be set
to?

STRICTLY the internal DNS server (set) which can resolve the DNS zone
which knows about AD.

They must not be set to use the gateway (which doesn't know about the
internal zone) or ISP DNS directly.

Currently I have the servers DNS set to the router pri, and internet DNS
sec.

The terms are PREFERRED and ALTERNATE (not primary and secondary
which are technical terms for server/zones.)

That is wrong -- this is your problem. They must be set to themselves and
optionally each other (that is, the INTERNAL DNS servers only.) DCs
are internal DNS clients too.

The router obviously is set with 2 Internet DNS addresses. The
workstations will not work unless they are set with the router as the pri
and
the internet as the secondary just as the server is set.

That is also wrong -- see above -- internal DNS clients (DCs, servers, and
workstations) must be set to STRICTLY the internal DNS server (set) which
can resolve the DNS zone which knows about AD.

I tried changing
the server to use itself as the primary and the router as sec and it was
not
able to browse.

Still wrong.

What is the proper setup? Thanks

To find the INTERNET, the internal DNS servers should be set to forward
to the Gateway (or for some people to the ISP) DNS.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)



.

Relevant Pages

  • 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)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
Loading