I'm desperate. One would think Online.net is a big ISP and has a decent an knoweldgable support, but my first try with them couldn't be worse.
I will try to keep it simple:
- Got a server, IP address is on the 195.154.0.0/16 range.
- 154.195.in-addr.arpa has 3 delegated NS: nsa.online.net, nsb.online.net and ns.ripe.net
- ns.ripe.net isn't working as a slave for the zone, throws NXDOMAIN
- As a result, one of each three RDNS queries for the 195.154.0.0/16 range is getting incorrect results.
Fix is as easy as removing ns.ripe.net from the delegation or correctly setting it up as a slave, whatever they want. The technician assigned to my ticket just refuses to recognize the problem and seems clueless about it. Escalation to a manager doesn't seem to work. Meanwhile, rDNS for the whole 195.154.0.0/16 is not working correctly and they couldn't care less.
I honestly don't know how this could be explained better to them so it can be fixed. If you have a dedicated server on the 195.154.0.0/16 range, you probably want to submit a ticket about it, since you are affected too. Maybe a different technician can see it and does understand how PTR delegations work.
Full ticket, for anyone interested: http://ift.tt/1wth28K
http://ift.tt/1dvHQ0Z
0 comments:
Post a Comment