PTR record not found

[tokunbo]

SYSTEM INFORMATION
OS type and version	REQUIRED
Webmin version	REQUIRED

Please could someone help with this:

I have an existing DNS server, Bind enabled, etc. I setup PTR records for a subnet of IPs(for ex: a.b.c.d/24) on it sometime back, and everything is currently working fine. It has just 1-master zone(domainA.com). DomainA is properly setup from the registrar.
Dig command locally gives correct results
If I do a PTR lookup from mxtoolbox.com, or any lookup portal, I see the correct results.

This week, I added another master zone(domainB.com - same registrar setup as above) and setup PTR records for a different IP-subnet(for ex: w.x.y.z/24) just the same way I set up the first one above.

Command dig -x ip-address @ns-server-ip shows the correct information locally on the server: I mean I can see the below info correctly.

;; ANSWER SECTION:
x.x.x.x.in-addr.arpa. 3600 IN PTR x.x.x.x.ptr-name/label

However if I try to do a remote PTR lookup from mxtoolbox or any lookup site online, it gives the error PTR record not found.

Is it not possible to have 2-master zones on same server? or is there something else I should do / define somewhere?

Note: PTR lookups for the first IP-subnet are working, while PTR records for the new IP-subnet arent, on same server, reachable from the internet

thanks for the help
TK

[verne]

are you sure that your ISP or hosting provider has allocated that space to you?

that is, does the public internet know your servers are responsible for the PTR records for your new IP range?

see if a dig +trace -x a.b.c.d on each IP shows you any important differences.

[verne]

also its very very rare that hiding your real IP and real domain names has any advantage — and by hiding them, it makes it just about impossible for anyone else to do any diagnosis from the outside

[Joe]

Most of the time your PTR record is out of your control. Your host owns the network block, not you. Some will delegate it on request, others will set it to a value of your choosing…almost never is it something that will Just Work if you set it up in your DNS server without explicit/informed cooperation from your hosting provider.