Hello, I have a strange DNS issue. I am trying to setup a PTR records for 168.192.in-addr.arpa It works on other non Linux systems. Here is the file with x being the subsituded for real name for all 64770 records. $TTL 3600 @ IN SOA x.x.com. root.x.x.com. ( 2007081201 ; Serial 3600 ; Refresh 1800 ; Retry 2419200 ; Expire 86400 ) ; Minimum ; IN NS @ IN NS x.x.com. 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. Which gives me for all 65770 ip addresses. named[3853]: master/168.192.in-addr.arpa:17923: ignoring out-of-zone data (1.0.168.192) I am trying to cover the entire 192.168 range. Any ideas on how to get this to work. -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
On Monday 13 August 2007 07:46:45 pm Boyd Lynn Gerber wrote:
Hello,
I have a strange DNS issue. I am trying to setup a PTR records for 168.192.in-addr.arpa
It works on other non Linux systems. Here is the file with x being the subsituded for real name for all 64770 records.
$TTL 3600 @ IN SOA x.x.com. root.x.x.com. ( 2007081201 ; Serial 3600 ; Refresh 1800 ; Retry 2419200 ; Expire 86400 ) ; Minimum ; IN NS @ IN NS x.x.com.
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.
Which gives me for all 65770 ip addresses.
named[3853]: master/168.192.in-addr.arpa:17923: ignoring out-of-zone data (1.0.168.192)
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 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. Good luck, J Wright -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
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 <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
On Mon, 13 Aug 2007 at 19:19, Boyd Lynn Gerber wrote:
I realy want to stay consistent across all platforms.
Please check the respective zone entries in your /etc/named.conf files, I think the reason for the inconsistency can be found there. My guess is, that on the platforms where it works the zone is named 168.192.in-addr.arpa, but on the linux box it is something like 0.168.192.in-addr.arpa . If you remove the "0." prefix, it should work with short entries in the zone file and no trailing dot:
0.1 IN PTR ip1921680001.local.x.com. 0.2 IN PTR ip1921680002.local.x.com. .. 255.254 IN PTR ip192168000254.local.x.com.
BTW, to further reduce the typing work and the size of the zone file, you can use the $GENERATE diretive: $GENERATE 1-254 0.$ IN PTR ip192168000$.local.x.com. $GENERATE 1-254 1.$ IN PTR ip192168001$.local.x.com. ... $GENERATE 1-254 255.$ IN PTR ip192168254$.local.x.com. This reduces the number of PTR lines from over 60000 to 256. cu Reinhard -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
On Tue, 14 Aug 2007, Reinhard Max wrote:
On Mon, 13 Aug 2007 at 19:19, Boyd Lynn Gerber wrote:
I realy want to stay consistent across all platforms.
Please check the respective zone entries in your /etc/named.conf files, I think the reason for the inconsistency can be found there.
My guess is, that on the platforms where it works the zone is named 168.192.in-addr.arpa, but on the linux box it is something like 0.168.192.in-addr.arpa .
If you remove the "0." prefix, it should work with short entries in the zone file and no trailing dot:
0.1 IN PTR ip1921680001.local.x.com. 0.2 IN PTR ip1921680002.local.x.com. .. 255.254 IN PTR ip192168000254.local.x.com.
BTW, to further reduce the typing work and the size of the zone file, you can use the $GENERATE diretive:
$GENERATE 1-254 0.$ IN PTR ip192168000$.local.x.com. $GENERATE 1-254 1.$ IN PTR ip192168001$.local.x.com. ... $GENERATE 1-254 255.$ IN PTR ip192168254$.local.x.com.
This reduces the number of PTR lines from over 60000 to 256.
zone "local.hbboys.com" in { file "master/local.hbboys.com"; type master; }; zone "168.192.in-addr.arpa" in { type master; file "master/168.192.in-addr.arpa"; }; Which is giving me the errors. These lines are exactly the same for all OS's. -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
On Tue, 14 Aug 2007, Reinhard Max wrote:
On Mon, 13 Aug 2007 at 19:19, Boyd Lynn Gerber wrote:
I realy want to stay consistent across all platforms.
Please check the respective zone entries in your /etc/named.conf files, I think the reason for the inconsistency can be found there.
My guess is, that on the platforms where it works the zone is named 168.192.in-addr.arpa, but on the linux box it is something like 0.168.192.in-addr.arpa .
If you remove the "0." prefix, it should work with short entries in the zone file and no trailing dot:
0.1 IN PTR ip1921680001.local.x.com. 0.2 IN PTR ip1921680002.local.x.com. .. 255.254 IN PTR ip192168000254.local.x.com.
BTW, to further reduce the typing work and the size of the zone file, you can use the $GENERATE diretive:
$GENERATE 1-254 0.$ IN PTR ip192168000$.local.x.com. $GENERATE 1-254 1.$ IN PTR ip192168001$.local.x.com. ... $GENERATE 1-254 255.$ IN PTR ip192168254$.local.x.com.
This reduces the number of PTR lines from over 60000 to 256.
Thanks this worked. I never knew of the GENERATE. -- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
participants (3)
-
Boyd Lynn Gerber -
james wright -
Reinhard Max