[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[public-dns-discuss] Re: Reverse DNS Lookup issues

Hi Alex,

Thank you for the update. We have now made sure that reverse for to returns ns1.cyient.com in APNIC which  seems to take some time to resolve as we just changed. Let me check and get back to you after some time.

Anil Kumar 

On Tuesday, February 20, 2018 at 10:02:39 AM UTC+5:30, Alex Dupuy wrote:
Well, ns1.infotech4all.com is the name server (by name) for the reverse zone. If that name cannot be resolved, you can have all the glue records in the world, and plenty of systems won't be able to resolve reverse PTR lookups, not just Google Public DNS.

Sending a PTR query for to returns ns1.cyient.com which does seem to resolve.

https://gwhois.org/ agrees, and says the reverse zone and IP address block are allocated out of APNIC. So you need to contact them and tell them to update the NS records for 160.76.110.in-addr.arpa to point to ns1.cyient.com instead.

You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dns-discuss AT googlegroups.com
To unsubscribe from this group, send email to
public-dns-discuss+unsubscribe AT googlegroups.com
For more options, visit this group at
For more information on Google Public DNS, please visit
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
For more options, visit https://groups.google.com/d/optout.