DNS reverse record

You could add a zone with Zonerunner, put a PTR record in there, make sure the delegations are in place and go wild with the records, but your ISP probably won't delegate their block to you if its not a big block of IPs, so they'll be the best place to start. Just request a new PTR for the IP with the value of the host.

Strictly speaking, your ISP could create a delegated zone for even a small block or even a single reverse record -- whether they'll do it depends on who they are.

if you do a dig -x "ip address" you'll see who "owns" that address space and figure out where you should get the PTR record added.

Hi DMC,

Many thanks for replying ... the problem is LC don't have zonerunner this feature is on GTM.... secondly the Public DNS is hosted by us internally into our network and for the first ISP we have the reverse lookup records on that DNS already but when we are creating the reverse records for our new ISP addresses on that DNS server its not working. I was thinking may be we have to do it on LC. can you throw further light on it.

Regards,

Any reply plss....

Actually, I don't know about your dns servers configuration, but I can assume that issue is with zones transferring. When you made changes for PTR records, is it work locally?

Hi Vitaliy,

I believe you have highlighted a very imp point here... of Zone transfer... the things is that the Public DNS is hosted internally into the network and there is another Public DNS server which is hosted somewhere outside, so how DNS zone transfer can effect this and how to find that the zone transfer is working or not this we need to find out but how?? The locally hosted Public DNS servers are on high preference. The reverse lookup is happening for the old Public IP set but for the new ones it is not working although its already created.... which commands can be used from the MS machines to check the reverse lookup for the address??/

From MS machines:

nslookup
> server [ip address of locally hosted dns server or another public DNS]
> set q=ptr
> ip address for wich you want check ptr record

Thanks buddy i was able to figure it out... my findings are revealing that there is some problem at the Ripe end for the new DNS entry which is causing this problem.