On Mon, 13 Aug 2007, james wright wrote: thanks...
On Monday 13 August 2007 07:46:45 pm Boyd Lynn Gerber wrote:
It works on other non Linux systems. Here is the file with x being the subsituded for real name for all 64770 records.
1.0.168.192. IN PTR ip1921680001.local.x.com. 2.0.168.192. IN PTR ip1921680002.local.x.com. 3.0.168.192. IN PTR ip1921680003.local.x.com. 4.0.168.192. IN PTR ip1921680004.local.x.com. ... 252.255.168.192. IN PTR ip192168255252.local.x.com. 253.255.168.192. IN PTR ip192168255253.local.x.com. 254.255.168.192. IN PTR ip192168255254.local.x.com.
Just off the cuff, I believe that you do not want the period at the far right of your IP address. Change:
1.0.168.192.
To:
1.0.168.192
On other OS's the . is mandatory or it fails. With out the . the is added to the base. Which would be 1.0.158.192.168.192. instead of 1.0.158.192. I tried it non the less and it still fails with the exact same message. I found that if I use 0.168.192.in-addr.arpa 1 IN PTR ip1921680001.local.x.com. 2 IN PTR ip1921680002.local.x.com. .. 254 IN PTR ip192168000254.local.x.com. Did work but then I have 256 files to do. I realy want to stay consistent across all platforms. 168.192.in-addr.arpa 0.1 IN PTR ip1921680001.local.x.com. 0.2 IN PTR ip1921680002.local.x.com. .. 255.254 IN PTR ip192168000254.local.x.com. Does not work. Same error.
Additionally, I think that you can safely remove some of the address. As everything is going to be between 192.168.0.1 and 192.168.255.254, I believe that you can get away with 1.0 then 2.0 then 3.0 and so on. I think that the reason that 192.168.0.1 is "out-of-zone" is that period on the right. I am no DNS wizard, but I am familiar enough to be dangerous. Hopefully someone will correct me if I am wrong. You could test with a much smaller file.
I am only going between them.
Ihis driving me crazy.
--
Boyd Gerber