DNS not resolving!!!!

[pgn...@yahoo.com.au]

Hello! I have a problem where I have 2 Domains in different forests (no
trust). Both Domains have DNS running and that works fine for when the
computers are working from their own domain however if a computer from
domain A connects to the Domain B Network the DNS no longer works. DHCP
is working fine and it is selecting the correct DNS server from that
domain but the nslookup is still trying to use the dns from the other
network.

Anyone got any ideas????? Really stuck here. Grrrrrrr

[Jorge Silva]

Hi

Inline

> however if a computer from
> domain A connects to the Domain B Network the DNS no longer works.

what do you mean with this?? The DNS stops working? what exactly does the
client describe all steps?

> DHCP
> is working fine and it is selecting the correct DNS server from that
> domain but the nslookup is still trying to use the dns from the other

- Make sure that you configure the Preferred DNS server in TCP/IP properties
on each Domain Controller to use itself as Primary DNS Server (If DC IP
Address is 10.0.0.1 then Dns should be 10.0.0.1).When adding an additional
DC to an existent Domain, do not configure the domain controller to utilize
its own DNS service for name resolution until you have verified that both
inbound and outbound Active Directory replication is functioning and up to
date. During the DCPromo process, you must configure additional domain
controllers to point to another domain controller that is running DNS in
their domain and site, and that hosts the namespace of the domain in which
the new domain controller is installed. More Info here:
Best practices for DNS client settings in Windows 2000 Server and in Windows
Server 2003

http://support.microsoft.com/kb/825036/en-us

- Make sure that every DNS server can resolve all existent domains in the
forest. (You can use Forwarding, Stub Zones or Secondary Zones).
DNS Conditional Forwarding in Windows Server 2003
http://www.windowsnetworking.com/articles_tutorials/DNS_Conditional_Forwarding_in_Windows_Server_2003.html

- Make sure that all clients only use their local(s) Dns Server. Note That
DNS client does not utilize each of the DNS servers listed in TCP/IP
configuration for each query. By default, on startup the DNS client will
attempt to utilize the server in the Preferred DNS server entry. If this
server fails to respond for any reason, the DNS client will switch to the
server listed in the alternate DNS server entry. The DNS client will
continue to use this alternate DNS server until: fails to respond to a DNS
query, or The ServerPriorityTimeLimit value is reached (15 minutes by
default). For more information:

Best practices for DNS client settings in Windows 2000 Server and in Windows
Server 2003
http://support.microsoft.com/kb/825036/en-us
How to configure TCP/IP to use DNS in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;305553

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

<pgn...@yahoo.com.au> wrote in message
news:1154496116.1...@s13g2000cwa.googlegroups.com...

[skhips]

Hi,

I am quite new at this so please use these comments to brain storm rather
than take as gospel, to achieve what you are tying to do we we have played
with two ways, one is create a secondary dns zone "copy zone" of e.g domain 1
onto two and domain 2 onto domain 1, including reverse zones, another was to
point their dns .root to a higher domain that would then act as the point to
find all the resoloution, I beleive stub zones is another way in W2K3 only
but not looked at that. We did have trusts in between forests but I dont
think that was needed for the DNS

[Kevin D. Goodknecht Sr. [MVP]]

pgn...@yahoo.com.au wrote:
> Hello! I have a problem where I have 2 Domains in different forests
> (no trust). Both Domains have DNS running and that works fine for
> when the computers are working from their own domain however if a
> computer from domain A connects to the Domain B Network the DNS no
> longer works. DHCP is working fine and it is selecting the correct
> DNS server from that domain but the nslookup is still trying to use
> the dns from the other network.

You mean it is using the DNS servers from the other domain?
It's likely a group policy on the other domain setting the DNS server list,
the DNS server list from a group policy overrides those from DHCP or even
manually configured DNS servers. I believe you'll find it in the registry
here:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================