Problem with Reverse DNS Lookup

[Kevin Darcy]

The in-addr.arpa servers are still delegating 92.140.in-addr.arpa to the old
address. You need to update this -- presumably with ARIN -- to reflect the new
server/address.


- Kevin

Lily Lee wrote:

> Thank you so much for the fast reply.  here is our situation:
>
> Recently we set up a secondary DNS.  We ran into a problem with reverse
> lookup.  Currently, when we type nslookup from machines outside our domain,
> (i.e. any machine outside our company), the reverse lookup (IP to Domain
> Name) doesn't work, but Domain Name to IP works.
>
> Before we set up the new secondary DNS, the original server name was
>                           aladdin.iii.org.tw
>                           IP address: 140.92.1.50
>
> Now the new name server is
>                           svr2.iii.org.tw
>                           IP address: 140.92.88.46
>
> We also put svr2.iii.org.tw as a Cname for aladdin.iii.org.tw
>
> When we are searching aladdin.iii.org.tw, the following result shows:
>
> Non-authoritative answer:
> aladdin.iii.org.tw      canonical name = svr2.iii.org.tw
> svr2.iii.org.tw nameserver = svr2.iii.org.tw
>
> Authoritative answers can be found from:
> svr2.iii.org.tw internet address = 140.92.88.46
>
> But when we are asking for 140.92.88.46,
> the following message pops up:
>
> dns.hinet.net can't find 140.92.88.46: Non-existent host/domain
>
> In order to solve our problem, do we need to register svr2.iii.org.tw with
> networksolutions? or ask ARIN to update our IP address record?
>
> Your assistance is greatly appreciated.
>
> Thank you in advance.