Conditional forwarder domain name length

I'm trying to create a Conditional Forwarders from Windows Server 2008 DNS to another domain Windows 2003  DNS, but I'm getting error: The server with this IP address is not authoritative for the required zone & when I apply it I get this error: A problem occurred while trying to add the conditional forwarder. A zone configuration problem accrued.

Is there a limit for the DNS Domain name?

The Domain Name I'm using is: abcdef_abcde.ab.abcdefgh.ab.ab
LVL 1
ManzourAsked:
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.

Cliff GaliherCommented:
Underscores in DNS zones are bad. Don't use them.
0
ManzourAuthor Commented:
Yeah...I know. It's already exist! What should I do?
0
Cliff GaliherCommented:
Probably nothing you can do if you don't control the actual problematic domain. Underscores are not in the DNS RFC, so windows isn't the only one that will have issues with underscores.

If you do control the offending domain, plan a migration ASAP.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

ManzourAuthor Commented:
It seems I was able to add now up to: abcdef_abcde.ab.abcdefgh.ab.a   !!!
0
ManzourAuthor Commented:
It's so wired!!! The domain ends by .us

It does not like .us !!! I can do .u  or .uss...etc but cannot do .US

 Pleas explain!
0
Cliff GaliherCommented:
Sounds like a direct conflict between an existing zone name and the conditional forwarder you are trying to create. This can occur if split-brain DNS was implemented previous to the decision to use conditional forwarders.
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
DrDave242Commented:
Do you already have a zone in your environment that would be considered a parent of the zone in your conditional forwarder? For example, if you're trying to create a conditional forwarder named abcdef_abcde.ab.abcdefgh.ab.ab as stated in your original question, you'll get that error if the DNS server already contains a zone with any of the following names:

abcdef_abcde.ab.abcdefgh.ab.ab
ab.abcdefgh.ab.ab
abcdefgh.ab.ab
ab.ab
ab
0
ManzourAuthor Commented:
That's correct, DrDave. I have this  zone: ab.abcdefgh.ab.ab.

So, what we should do?

Which one is better: Conditional Forwarder or create new zone under Forward Lookup Zones as a Secondary zone?
0
DrDave242Commented:
Since you've got the parent zone in your environment, you can use a delegation for the child zone.
0
ManzourAuthor Commented:
I meant in general! We have multiple forests and domains and the DNS and each environment has its own DNS (Mostly AD Integrated)  .
0
DrDave242Commented:
In general, you can use a delegation or stub zone in this situation, but a conditional forwarder won't work if the parent zone already exists on the DNS server.
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
Windows Server 2008

From novice to tech pro — start learning today.