Reverse DNS lookup fails for subnets smaller than /24
Bug #1931838 reported by
Björn Tillenius
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Christian Grabowski | ||
| 3.0 |
Fix Released
|
Critical
|
Björn Tillenius | ||
Bug Description
If you have a subnet that is smaller than /24, like a /25, the glue records aren't generated properly in the bind config.
So if you try to do a reverse DNS lookup for an IP in that subnet with `dig -x`, you won't get the hostname it corresponds to.
This was already fixed in master,
fdd0c41bba6b758
MAAS 3.0.0~rc2-
Related branches
~bjornt/maas:reverse-dns-3.0-backport
- MAAS Lander: Approve
- Björn Tillenius: Approve
-
Diff: 98 lines (+32/-19)3 files modifiedsrc/maasserver/dns/tests/test_zonegenerator.py (+3/-0)
src/maasserver/dns/zonegenerator.py (+6/-2)
src/provisioningserver/dns/zoneconfig.py (+23/-17)
| Changed in maas: | |
| status: | New → Fix Committed |
| assignee: | nobody → Christian Grabowski (cgrabowski) |
| importance: | Undecided → Critical |
| Changed in maas: | |
| milestone: | none → 3.0.1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| Changed in maas: | |
| milestone: | 3.0.1 → 3.2.0-beta1 |
To post a comment you must log in.
