Re: DNS Design Question--revisited



> Well, I meant to get rid of or disable the NW DNS services since the
version
> you are using cannot support AD's requirements. Choosing not to
configure
> DNS on the NW servers is the same thing that I was saying.
>
> But that leads to this statement confusing me:
> >...I can chose not to
> > configure dns on Netware, but removing
> > it from all branches is not an
> > option at this point.
>
> Do you mean you are not choosing to configure DNS on NW, and that
means you
> won't be using DNS, correct? Then what do you mean by removing it from
all
> branches? Meaning DNS or the NW servers themselves?

What I meant above is this: I inherited a Netware network with dns not
ever fully configured. A couple of branches had dns, most did not. But
we were running IPX/SPX and the related services. We started adding w2k
servers as applications that were needed, needed w2k. This led to domain
controllers. Which led to this present situation. Before moving forward,
I wanted to get a clear picture of what I needed to do, hence this post.

>leaving it the way it is, is a sloppy design that will lead to problems
and complicating resolution in your
> network (such as what you are trying to get help on now).
I agree and now understand where problems would come from.


>If you dont want to use W2k DNS, then you can use BIND 8.2.3 or
> newer, but for your sake, whatever you use, retire the NW DNS servers
since
> they do not support your requirements.

> Ace

Thanks again, Ace.

.



Relevant Pages

  • Re: Changing IP adressing on Win 2003 servers.
    ... For non-SBS servers and this Windows Server 2003 is running the critical services, like Directory service, DNS, DHCP etc, we need to perform the adjustments manually. ... We should clean DNS cache on all computers and point the computers to use the correct DNS and WINS servers. ... We mainly support break-fix issues in the newsgroups, if you need a more detailed action guide, please consider Microsoft Advisory Services to design a solution specifically for your environment and requirements. ...
    (microsoft.public.windows.server.setup)
  • Re: Server loses network - bizzare behavior
    ... doing anything to the hardware on these servers. ... Meanwhile I'll see if disabling the unused NIC's helps, and if not, I will ... All errors, except id 12, states about connectivity to the domain DNS servers, ... see Help and Support Center at ...
    (microsoft.public.windows.server.general)
  • Re: Server loses network - bizzare behavior
    ... doing anything to the hardware on these servers. ... All errors, except id 12, states about connectivity to the domain DNS servers, ... see Help and Support Center at ... Then a few minutes later in the Application logs this error start ...
    (microsoft.public.windows.server.general)
  • Re: Help SMPT Errors
    ... FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your ... it may mean that your DNS servers did not respond fast enough). ... INFO NS records at parent servers Your NS records at the parent servers ... PASS Parent nameservers have your nameservers listed OK. ...
    (microsoft.public.exchange.admin)
  • Re: Server loses network - bizzare behavior
    ... As said before disabling unused NIC's and if exist removing the records in DNS can help. ... I have 10 other servers that are not having any network ... see Help and Support Center at ... Then a few minutes later in the Application logs this error start ...
    (microsoft.public.windows.server.general)