[BUG] Create/update PTR from forward zone seems broken for some IP addresses #408
Comments
Willy, normally I would check the code myself for a fix, but am currently not able to, sorry! |
Maybe a regex that removes the first octet from, but is set to 'greedy' and removes every instance of that value? So something like: |
This is now fixed in fmDNS 3.2 and later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Replace everything between stars with current version of your facileManager and module installations:
fM Version : 3.1.1
fmDNS Version : 3.1.2
In raising this issue, I confirm the following (please check boxes, eg [X]):
(BUG | ISSUE) Expected Behavior:
Exempt from log for forward:
Updated a record (test) with the following details:
Domain: domain.com
Type: A
Name: test
Class: IN
Type: A
Value: 10.1.7.177
Status: active
Exempt from log for reverse:
Updated a record (177.1) with the following details:
Domain: 10.in-addr.arpa
Type: PTR
Name: 177.7.1
Class: IN
Value: test.domain.com.
Status: active
Domain Id: 12
(BUG | ISSUE) Actual Behavior:
Exempt from log for forward:
Added a record with the following details:
Domain: domain.com
Type: A
Name: test
Class: IN
Value: 10.1.10.177
Status: active
Exempt from log for reverse:
Added a record with the following details:
Domain: 10.in-addr.arpa
Type: PTR
Name: 177.1
Class: IN
Value: test.domain.com.
Status: active
(BUG | ISSUE) Steps to reproduce:
Just create an a-record with PTR enabled:
There seems to be an issue with the creation and updating of reverse/PTR records from the forward zone, the reverse entry ends up being incomplete and missing part of the address.
The text was updated successfully, but these errors were encountered: