DNS Forwarders not working for out other Domain

I have a problems with Conditional Forwarding in Windows 2003 DNS.

First the Background.
We have a active Directory Domain called something.com which DNS in integrated in AD.
This Domains has 2 DNS servers, which are also ours DC and GC
The We have an Unix Domain Called something.net but also with have an Internet domain called something.net too

The Unix Domain has its own DNS server and here where the problem begins.

The Unix Domain are only use by internal application use by the servers.
The NT Domain its use for End Users.

So my problem is that We had set up a condition that when you try to do a query for the domain something.net should first go to the Internal Domain something.net and if is not found there go to the DNS of our Internet Domain.

But for some reason this isn't working .

I try an NSLOOKUP to ftp.something.net should found it on the Internet domain but I just received this error
Default Server:  DC1.something.com
Address:  172.22.xx.xxx

Server:  DC1.something.com
Address:  172.22.xx.xxx

*** dc1.something.com can't find ftp.something.net: Non-existent domain

Its like isn't even looking in the right place.

I ran a DCdiag test:dns and all went just fine, no even a single failure
We have our DNS forwarders are setup as follows.


ALL other DNS Domains
are pointing to 2 of ours Internet DNS

Pointing to out DMZ DNS

Pointing to our Unix DNS which then point to the correct address for our Email Domain

is pointing to our Unix Domain DNS & to our Internet DNS

Thank you
Who is Participating?
NehemothConnect With a Mentor Author Commented:
nobody gave an answer so I will close it.
If the internal DNS server hosts something.net, it will never forward any requests to the external DNS server hosting something.net.  It will just look in it's own something.net zone and if it can't find the record you're looking for, it will return a 'not found'.  You need to add all the external something.net records to the internal something.net DNS server.
NehemothAuthor Commented:
Yes I understood that.

By my problems right now are from something.com to something.net be the internal or the external
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

NehemothAuthor Commented:
I also found this error in our Event Viever

Event Type:      Error
Event Source:      DCOM
Event Category:      None
Event ID:      10009
Date:            4/8/2009
Time:            9:07:41 AM
User:            N/A
Computer:      SVRDC1
DCOM was unable to communicate with the computer 200.42.xxx.xx using any of the configured protocols.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The IP Correspond to our Internet DNS server
NehemothAuthor Commented:
Still waiting for the answer
NehemothAuthor Commented:
Still, someone knows?.
All Courses

From novice to tech pro — start learning today.