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