Clarification of Answer by
funkywizard-ga
on
01 Nov 2002 22:05 PST
When people do a reverse dns lookup on your ip address, it will indeed
map to something that your isp has designated, for example here is a
traceroute:
C:\>tracert 24.237.4.113
Tracing route to 113-4-237-24-cable.anchorageak.net [24.237.4.113]
This clearly shows that 113-4-237-24-cable.anchorageak.net will
resolve to the ip address 24.237.4.113, and that doing a reverse
lookup on the ip 24.237.4.113 will get you
113-4-237-24-cable.anchorageak.net.
However, for your use, this is not necessary. In the example above,
this ip address is used to host my website, akddr.com, along with
several other websites, such as akghetto.com and aksearch.net. Any
number of domain names may point to a single ip address, and in fact
more than one dns server may point to an ip address. If you absolutely
must have a reverse lookup respond with your server address, you will
have to contact your isp and request that they change their reverse
lookup table. In order to set your own reverse lookups, you will need
to own your own class c ip address range (x.x.x.y, where y is any
value 0-255, and the x.x.x. is assigned to you specifically).
None of this will affect the performance of running your own dns
server to maintain a list of websites that reference your server. for
example, www.akddr.com will resolve to 24.237.4.113 even though the
isp maintains that the reverse lookup of 24.237.4.113 will not point
to www.akddr.com. All that must be done is to inform your domain
registrar of which dns server you would like to use for resolving your
domain names.
I trust this answers your question, but if it does not, do not
hesitate to request further clarification.