Reverse DNS entry matches name server name (Address03)

[svoon]

hi,
not sure if this makes sense to report - it would require dedicated IPs for each NSSET. Considering the IPv4 space, this goes bit against to share IPs for different domain names.
At the same time, I don't want to have in 'our' NSSET, which we provide to our customers, (host)names of our datacenter provider, which provides host 'his' nameservers as secondary/third/...

And having this even as a 'Notice', prevents us to have zero findings.

[matsduf]

Could you explain what change you would like to see or what problem you see in Address03? What do you mean by "NSSET"? Thanks!

[svoon]

Address03
Notice
Nameserver b.ns.foo.bar has an IP address (x.y.z.x) with mismatched PTR result (ns2.provider.com.).
Nameserver c.ns.foo.bar has an IP address (x.y.z.y) with mismatched PTR result (ns3.provider.com.).

[svoon]

my point was to remove this Address03 check completely

[matsduf]

Mismatching reverse name is a bad idea. Why do you see it as a problem to report that?

[svoon]

the problem is described in the original post:

1. if you are using NS servers from your datacenter/housing/hosting provider, he uses his own PTR
2. then you have to have in your NSSET provider's hostnames (which is weird for my customers), or the PTR simply not match
3. Or, I would need to ask my provider to put there additional IP addresses to his Nameservers, which will have 'my' PTR - which is from IPv4 address space non-sense.
   Same with all other services, multiple 'domains' are hosted/provided on one IP. Should we be worried if www.domain.com points to IP which's PTR doesn't match?