• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 848
  • Last Modified:

RFC2317 classless reverse zones question

I have this zone 28.35.169.12.in-addr.arpa.db

32/28.35.169.12.in-addr.arpa. 3600 IN      SOA      ns1.foo.com. domains.foo.com. 2009060800 21600 3600 604800 3600
32/28.35.169.12.in-addr.arpa. 3600 IN      NS      ns1.foo.com.
32/28.35.169.12.in-addr.arpa. 3600 IN      NS      ns2.foo.com.
34.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      www.accu-sark.com.
35.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      crm.accu-sark.com.
36.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      osc2or.accu-sark.com.
38.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      mail2.accu-sark.com.
43.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      mail.accu-sark.com.
46.32/28.35.169.12.in-addr.arpa. 3600 IN PTR      ext46.accu-sark.com.

I am getting an error of when trying to import this zone to another IPAM management product

RFC2317 prefix must not be empty for classless reverse zones

My question is, how to fix this to make it compliant?
0
richsark
Asked:
richsark
1 Solution
 
Chris DentPowerShell DeveloperCommented:

There's nothing wrong with the zone above. I'm not sure why it would complain about it. You'd have to share the name of the IPAM product, and we'd have to hope they have some kind of documentation on classless reverse lookup zones.

Chris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now