up vote 0 down vote favorite
share [g+] share [fb]

it would be $ORIGIN 113.168.192.IN-ADDR.ARPA. for a 255.255.255.0 netmask

but what would the origin be for a netmask of 255.255.128.0

link|improve this question
65% accept rate
feedback

2 Answers

up vote 2 down vote accepted

If I understood you correctly, you are looking to create a reverse DNS allocation for /17 with one $ORIGIN, thats not possible and for allocations larger than a /24 block you would have to breakdown your /17 into 128 sets of /24 and use individual sets for reverse DNS.

link|improve this answer
there are other ways of doing this (e.g. with CNAMEs), but this is pretty much the easiest. – Alnitak Nov 4 '11 at 11:38
do i need $ORIGIN at all? – The Digital Ninja Nov 4 '11 at 11:46
@Alnitak, but still one would be required to be put a PTR record somewhere right, or did I get it wrong ? $ORIGIN is to append whatever comes after it ($ORIGIN) to your individual records, so yes put it, saves you some typing. – Gaumire Nov 4 '11 at 11:53
I guess a better question would be what is the simplest way to add reverse dns for all my virtual machines? I have it set up with a split horizon dns and want the local ips to resolve to names. I dont want to have to create 128 files. – The Digital Ninja Nov 4 '11 at 12:12
@Gaurmire I was talking about RFC 2317 - tools.ietf.org/html/rfc2317 – Alnitak Nov 4 '11 at 13:04
feedback
up vote 0 down vote

The reverse DNS has nothing to do with a netmask. It is just the PTR of an IP.

So the answer is: The same!

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.