Proper DNS configuration

Having problems with DNS (Mostly Reverse DNS) and I want to make sure I have a proper setup before I have someone else do it for me.

A little background:
- our email/web is hosted my another server. My exchange server (using sbs2k3) gets our e-mail using MS POP3 connector. (trying out POPBeamer as well).

- currently sending out mail through dns rather than smarthost. I have changed the recipeint policy in Exchange to reflect our regeistered domain e-mail address rather than the local address that is not registered (domain.local)

- Because of reverse dns lookup, have setup those servers with this service turned on, to route to our smarthost instead of dns (very slow)

I'd like to setup our dns to resolve the lookups without having to host our own e-mail (Been told its allot easier this way)

I am in the process of trying to get our isp to associate our static IP with a subdomain on their network. Once they do that do I need to do anything with my dns server to reflect this once they update their info? My current zones on the DNS server only reflect internal IP addresses, nothing reflects the public (static) IP.

Am I heading in the right direction? Appreciate the feedback.

ok, so you want your ISP provided IP to resolve to a domain. You're having your ISP set this up if they will. Well, if your ISP just has the IP resolve to a domain for you then you don't need any additional configuration to your server.

If there's some other issue you're wanting help with as well, rephrase your question. It's ironic that I have a harder time understanding what people are saying than actually fixing their problems.

So its all up to the ISP and their DNS servers. I do not have to have anything setup on my server to reflect this as well? No reverse DNS pointing to the static IP? Nothing pointing to the ISP's DNS Servers? Granted, I can send and receive quite well except for the Rev DNS people, but it seems like some e-mail is lost here and there and I want to make sure that its nothing on my end.

(Okay multiple questions, but they all deal with the same thing) (As for the hard time understanding, if your good at something it all sounds easy to you until you get a description from someone that has no clue. I have the same problem in my line of work, and I am sure someone says the same on something that you do not know either.)

yeah, you could say that since I know the terminology and have a kind of fundamental understanding about this, that hearing people's made-up terminology or skewed perspective would throw me for a loop. But many times it's just cause people go on about things I don't need to know. For example I've reduced your entire post to "my IP needs to resolve to a domain, what do I do!?". Course, knowing what the IP is helps, but anyway, I ramble...

Let's see. yep, you heard me right. You don't have to point anything at anybody, you don't have to do anything with your dns server. You just make your ISP do their thang, and if you want me to make sure they're doing their thang or have done their thang yet, just give me the IP to investigate.

Some ISP's like SBC however will delegate resolution to your dns server. In that case there is more work you need to do. But I'm assuming your ISP will resolve the IP to a domain itself. This is why it's helpful if I knew the IP. I might have some insight into how your ISP does things.

Cool...thanks for the help.... I tried to get the same info from what are supposed to be gurus at the Microsoft Small Business Server Newsgroup/Forum (Since that is the package I am using) and all they could tell me is run SMTP for incoming mail. Even though my original post was "outgoing mail with DNS". I have gotten used to trying post all the info, that I forgot what a simple question is. But again...thanks!

Oh, my IP or ISP's?? Rather not post mine, but the ISP's is 204.120.202.2