Internal DNS with hosted web site

Hello and thanks for helping in advanced.
First my situation
I have a windows 2000 domain called cameta.com with about 30 computers
We own the domain name cameta.com which is hosted at earthlink along with our email.
We use a win2k server for our smtp server.

1st question.
What record do i need to add to my forward lookup zone so when a internal computer in my domain types in URL he will go to earthlink where our site is hosted instead of the dns server thinking that cameta.com is internal because we have the same domain name?
2nd question
if we send email to ourselves ex. from URL to URL it dosent go through because the smtp server thinks that cameta.com is internal. i think that I need earthlinks fqdn to put in dns server but i dont know please help
thanks

I have exactly the same problem and it is giving me high blood pressure

Our Windows 2000 domain is initial-approach.co.uk and our website (hosted on Demon) is initial-approach.co.uk. If the workstations are set up to obtain a DNS server address from our own Windows 2000 server, you can't access either URL or URL, both of which appear in the forward lookup zones. All other www sites are fine.

If I change the workstations TCP/IP configurations to use Demons servers for DNS addresses internet access is OK, but everything else slows to a crawl as of course every DNS request (including internal) is being routed over the internet to Demon instead of being dealt with by our server.

I am sure there is a simple solution but I can't find it

Help please!

*grumble* it seems nobody wants to use BIND lately. It is hard for me to help you guys. But I do know what's wrong, you can't connect to your public IP. What you need is for the DNS server to return private IPs when private clients query the server. This technique is called "Split DNS" or "Split Horizon". I know how to set this up in BIND, I read how to do it in djb's tinydns, but I have no clue how to do it in Microsoft DNS Server. So it is my suggestion that you look for an option with the word "split" in it. You will have to specify the local IP branch that will have privatized information.

There are other solutions. You could setup a different dns server to handle LAN requests. You could specify the private IPs for all local domains in hosts files.