Thanks Rod!! and Phillip!! for your help. I had done what you had
mentioned in your replies. I was double checking with experts to make
sure it was right. And it seems like I got it right.
Oh yeah, the TTL is set very LOW for just in case there was a goof up
on my side :) . I will be changing them soon.
Once again, Thanks a bunch for your help guys!!. I really appreciate
it.
Cheers!
-Parvinder Bhasin
On Jun 28, 2008, at 10:14 PM, Rod Dorman wrote:
On Saturday, June 28, 2008, 16:32:18, Parvinder Bhasin wrote:
...
How should I write out the config in named.conf to reflect the
reverse
zone?
Lets say my network is 192.168.1.0/25.
...
2.1/25.1.168.192.in-addr.arpa. 300 IN PTR foobar.mydns.com
It's simpler if you establish an origin
$ORIGIN 1.168.192.in-addr.arpa.
then you just have to use the identifying octet
2 300 IN PTR foobar.mydns.com
From the way you worded "Lets say my network is" I'm guessing that
your
192.168.1.0/25 is just an obfuscation of an allocated public
range. If
so, whoever is authoritative for 168.192.in-addr.arpa. has to
delegate
0.1.168.192.in-addr.arpa. thru 127.1.168.192.in-addr.arpa. to
you in
order for the outside world to see your PTR records.
BTW, why only a 5 minute TTL?
--
[EMAIL PROTECTED] "The avalanche has already started, it is too
Rod Dorman late for the pebbles to vote." - Ambassador
Kosh
