Project

General

Profile

Feature #17003

Allow a "rewritemap" for PTR records to support RFC2317

Added by Andreas Rogge almost 6 years ago. Updated almost 6 years ago.

Status:
Ready For Testing
Priority:
Normal
Assignee:
Category:
DNS
Target version:
-
Difficulty:
medium
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

RFC2317 describes ways how to do Classless IN-ADDR.ARPA delegation.
It boils down to this: your provider sets a bunch of CNAMES where you would expect the PTRs usually. These CNAMES point to a different zone that is under your control.

Using the network 192.0.2.128/25 i've seen the following zone variants:
- 2.0.192.in-addr.yourdomain.tld
- 128/25.2.0.192.in-addr.arpa
- 128-25.2.0.192.in-addr.arpa
- 128-255.2.0.192.in-addr.arpa

As there is no really sane way to do this i hereby suggest the following solution:
- add a new configuration option "dns_ptr_rewritemap" that may contain a hash of { regexp => replacement } to all DNS providers where RFC2317 might occur (i.e nsupdate, nsupdate_gss, dnscmd)
- add a new function rewrite_ptr() that rewrites the ptr according the the map configured (or do nothing if no map is configured)
- make create_ptr_record() and remove_ptr_record() call rewrite_ptr() on the PTR to be created before passing it down

History

#1 Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/466 added

Also available in: Atom PDF