Why isn't the TLD being used when joining a domain?

I'm working on a test Active Directory domain: domtest.local
When I'm joining an XP PC to the domain, it only works if the domain I use is domtest, if I try domtest.local the PC cannot connect. The eventual idea is to have a domtest.local and a domtest.com domain structure and I'd like to know why the .local isn't working.
The computer does show in the Computers OU.
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.

You are pointing to a DC for DNS?

Can you ping domain.local?
CapricaAuthor Commented:
Yes, I can ping domain.local. The server is DC, DNS, DHCP, AD. It appears to be working properly, it's the domain joining that has me puzzled and makes me suspicious that all may not be right.
As long as you can ping the domain via the "domain.local" address, and the client is pointed towards the DC for DNS I can think of no reason you couldn't join the domain via its FQDN.

Can you try it again on a different PC (if you have it) and immediately after the failure look at the logs of both the DC and workstation for relevant entries?

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
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

CapricaAuthor Commented:
Thanks, will give it a try. I'll have to build a machine, I'll post back once it's done.
CapricaAuthor Commented:
Thank you for you help, after checking the logs and then going through the SRV records it turns out some SRV records were missing. Using the Windows Support Tools netdiag /fix has corrected the issue.
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 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.