Re: DNS help in AD

Tech-Archive recommends: Fix windows errors by optimizing your registry



That would be caching. When the cache is cleared or expires, they may stop
working again. You shouldn't have many forwarders... move them back to the
top.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Gonzo" wrote:

Thanks, it works a treat now using forwarders. Although it didn't work at
first until I moved them to the top of the list. I then movedthem to the
bottom of the list and they still work. Maybe some sort or learning going
on?


"Steve B" <SteveB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CEDAF033-C0B5-4284-885B-27B9C3854FB8@xxxxxxxxxxxxxxxx
As you mention I would go for forwarding instead. Your clients need to
see
your DNS Server for AD authentication etc etc.

"Gonzo" wrote:

Hi,

First of all sorry for my spelling, very tired.

1.) Correct

2.) This is another company, just a VPN to access reources.

3.) Spooky, that's what I'm goign to try instead. We already have 2 Ip's
there to resolve internet pages, I'm going to add their 2 DNS servers,
then
update the routing across the VPn.

Let me know your thoughts


"Steve B" <SteveB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D1DC8D06-A482-4B1A-8520-1C19CF533381@xxxxxxxxxxxxxxxx
Hi,

Just to understand your setup a little more;

1) There DNS Servers are hosting a separate domain e.g. abc.com, whilst
your
DNS servers manage xyz.com for example?

2) Was there a particular reason for installing a DNS Server in the
remote
office? Is there a DC from your domain there?

3) Is there a reason you didn't use Windows 2003 Conditional Forwarding
to
resolve their names?

"Gonzo" wrote:

I'll try and explaing this the best I can.

We have a single AD 2003 domain.

We have just added a VPN to our office in the US. Tottally separate
networks/domains.

I can ping there DNS servers and web servers.

They have asked me to add their DNS server to our DHCP scopes which
is
done.

We now have our 2 DNS servers and their 2 DNS servers, the order is
ours
then theirs.

If I ping our servers names it resolves, if I ping the there DNS names
it
resolves, but I then can't ping any of our server names, it's as if my
pc
is
only suing their DNS servers and not ours first. Is this right and
the
best
way for me to ping resolve there DNS names?

I was thinking of removing the DNS servers and just manually putting
in
the
names into DNS as A hosts, problem is we are on gb.nji.local and they
are
on
nh..net

Do I have to add a zone or something to our DNS to resolve them?

Thanks





.



Relevant Pages

  • Re: novice: problem adding second domain
    ... I noticed that I can ping by name across ... its own IP and our gateway to the internet for that subnet as DNS servers. ... > Forwarders and the IP of its DC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: novice: problem adding second domain
    ... I noticed that I can ping by name across ... its own IP and our gateway to the internet for that subnet as DNS servers. ... > Forwarders and the IP of its DC. ...
    (microsoft.public.windows.server.dns)
  • Re: novice: problem adding second domain
    ... I noticed that I can ping by name across ... its own IP and our gateway to the internet for that subnet as DNS servers. ... > Forwarders and the IP of its DC. ...
    (microsoft.public.windows.server.networking)
  • Re: Very Critical issue
    ... I would suggest you disable one of them and even if this doesn't resolve the issue I wouldn't ever have them setup on a dc. ... create forwarders in DNS so that requests for the a.com domain will be forwarded to the a.com DNS servers and b.com requests to the b.com forwarders. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT 4.0 DNS integration with 2003 AD DNS
    ... if we want the NT4.0 domain clients to be ... > able to resolve the hosts in the 2k3 domain how do we go about ... > topology so that all queries unresolved by the NT4.0 DNS servers are ... If the 2k3 DNS server have a good set of dependable forwarders ...
    (microsoft.public.windows.server.dns)