Reverse DNS Windows 2000 Server

[rwies]

I have been running an internet server with my own DNS for some time. I have never messed with reverse lookup zones. We are having a problem sending emil to some addresses such any aol address. The error messge we get is a problem with reverse lookup.

I have tried several thins to get the reverse lookup working but I can't seem to hit on the solution.

When I do a nslookup on one of my ip's with a mail server running this is what I get:

C:\WINDOWS\system32>nslookup 65.38.21.180
*** Can't find server name for address 65.38.21.170: Non-existent domain
Server: dnscache2.tulsaconnect.com
Address: 65.38.1.4

*** dnscache2.tulsaconnect.com can't find 65.38.21.180: Non-existent domain

65.38.21.170 is my server ip address, my service porvider is Tulsa Connect.

I don't have any entries in the reverse lookup section at this time. If anybody can give me exact instructions on how to set up the reverse lookup I would greatly appreciate it.

Ron

 

[ShackDaddy]

Here's the deal. You can't create your own reverse lookup addresses unless you own the whole block/subnet. So you have two options. Either have TulsaConnect make a reverse lookup address for you on their server, or make a config change on your server. They probably won't do the former for you, so here's what you have to do.

From a system outside of your network, do a traceroute on your own server IP. Watch the name resolutions as it jumps from hop to hop. When it reaches your server IP, look at the name that it gives. It will probably be something weird that ends with 'tulsaconnect.com'. That's a key piece of information.

Now go into the Exchange Manager. Go into your Default SMTP Virtual Server properties. Choose the Delivery tab. Click the Advanced Delivery button. Take that FQDN (the named (not IP) address you took from the trace of your server address) and put it into the Fully Qualified Domain Name field. Now when your server sends mail out, it puts its name in the header, and when the destination server does a reverse lookup, it finds the proper information that TulsaConnect put in their reverse DNS zone for the subnet they pulled your IP from.

Hope that helps,

ShackDaddy