Conditional DNS forwarding issues server 2003

I am having an issue with conditional DNS forwarding on server 03.

We have two domain we are looking to create a trust between. One is Server 08r2 DCs on functional level 08r2. The other consists of Server 03 DCs running in 2000 native.

We created conditional forwarders on the DNS servers for both domains. The ones in the 2008r2 environment work great. They are not however working on the server 2003 DCs. I then noticed that Server 08r2 servers in the older domain can resolve names from the new domain just fine. So the issue seems to be with just server 03. And in this case, it is a crucial one as the DCs are the ones we need to resolve the FQDNs so we can create the trust. :)
LVL 10
Schuyler DorseyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Schuyler DorseyAuthor Commented:
I verified it's not a firewall issue. I can nslookup anything fine when I specific the other DC as the server to use.
0
Schuyler DorseyAuthor Commented:
Also... I am specifying the FQDN when trying to resolve.
0
Matt CoughlinCommented:
Hello Schuyler,

Would raising the functional level of the older servers to match the newer servers help? Just a thought.
0
INTRODUCING: WatchGuard's New MFA Solution

WatchGuard is proud to announce the launch of AuthPoint, a powerful, yet simple, Cloud-based MFA service designed to eliminate the vulnerabilities that put your data, systems, and users at risk.

Schuyler DorseyAuthor Commented:
I wanted to do that first.. trust me! This is a high-security environment with a lot of crucial A.D. integrated apps running in the older production network. Getting clearance to raise it would take an act of god. :)

I did figure out out though! One of the DNS servers was missing the configured forwarders. It was present on 2/3 DCs. Once I added it to the last DC, I started working.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Matt CoughlinCommented:
Awesome work!

And I agree, with all of those legacy AD integrated apps floating out there... I wouldn't raise it!
0
Schuyler DorseyAuthor Commented:
I was able to solve it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.