New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse zone and subnet #284

Closed
lchanouha opened this Issue Jan 15, 2016 · 10 comments

Comments

Projects
None yet
2 participants
@lchanouha

lchanouha commented Jan 15, 2016

I can't create reverse zone for which I have a subnet different that /8 /16 /24.

Eg i own revUNR.10.20.30.in-addr.arpa and not directly the 10.20.30.in-addr.arpa.

My records should be 1.revUNR.10.20.30.in-addr.arpa

Here is an RFC to stick to : http://www.ietf.org/rfc/rfc2317

A workaround could be to clone the 10.20.30.in-addr.arpa to revUNR.10.20.30.in-addr.arpa but the software doesn't actually allows that.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 15, 2016

fmDNS does support classless zones. When creating the zone, just enter it as x.y.z/cidr. For example, 30.20.10/28.

@lchanouha

This comment has been minimized.

lchanouha commented Jan 15, 2016

This time i do not understand; Am i suppose to entre the network/cirdr as "Domain Name" ?

I still get "Invalid zone name." when i enter "192.168.0/24"

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 15, 2016

My mistake - it won't accept the cidr notation, but you can specify the range. For example, a valid domain name would be 1-128.10.20.30.in-addr.arpa.

@lchanouha

This comment has been minimized.

lchanouha commented Jan 16, 2016

Your rule "/^(\d{1,3})-(\d{1,3})$/" is too restrictive.(/server/fm-modules/fmDNS/classes/class_zones.php:1229). The reverse zone i got from my ISP for my subnet does not fit it.
I think it should be near '([a-zA-Z0-9-]*)' (or include an option to force creation for such cases). I think you did it for auto PTR generation and I know this isn't the best way to handle subnets (http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/avoid-rfc-2317-delegation.html) in reverse zones, but i can't change my ISP policy...
To keep PTR generation feature working i thought to simply clone zone from 0.20.30.in-addr.arpa to revUNR.10.20.30.in-addr.arpa.

Sorry for my english

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 16, 2016

I'm sorry, but I don't understand what revUNR means in an IPv4 reverse zone.

@lchanouha

This comment has been minimized.

lchanouha commented Jan 16, 2016

Nothing. That's a custom name to identify the zone. It could be office1, office2, ...
Here is my complete zones:
revPOLE.49.49.193.in-addr.arpa
revUNR.249.48.193.in-addr.arpa

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Jan 16, 2016

RFC2317 was referenced when support for classless subnets was added per #69. I don't see how revUNR follows the RFC as the delegation is for IPv4 octects which do not contain alphabetical characters. Any help to understand would be appreciated.

@lchanouha

This comment has been minimized.

lchanouha commented Jan 16, 2016

As of $ 5.2 in this RFC

As a result of this method, the location of the zone containing the
actual PTR records is no longer predefined. This gives flexibility
and some examples will be presented here.

The name of the reverse zone is not fixed to the start ip address to end. It could be an arbitrary name.
You have for eg. another template presented:
129.128/26.2.0.192.in-addr.arpa.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Mar 31, 2016

This will be supported in the next release.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Apr 25, 2016

v2.2 has been released and contains this fix.

@WillyXJ WillyXJ closed this Apr 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment