Web Hosting Talk







View Full Version : Reverse Zone


Fremont Servers
04-21-2002, 02:47 PM
Is it normal when provider doesn't delegate you the
reverse zone, that's why you cant reverse resolve the IP. If you run:

nslookup ns1.gdznet.com ns1.gdznet.com
nslookup 66.220.13.162 ns1.gdznet.com


Does anyone have a clue how to fix this?

Is this a misconfigure in the box or the ISP side?

dot.K
04-21-2002, 04:09 PM
Originally posted by Asia
Is it normal when provider doesn't delegate you the
reverse zone, that's why you cant reverse resolve the IP. If you run:

nslookup ns1.gdznet.com ns1.gdznet.com
nslookup 66.220.13.162 ns1.gdznet.com


Does anyone have a clue how to fix this?

Is this a misconfigure in the box or the ISP side?

Can you please post the Reverse Zone file you are using ?

Normally spoken, if the ISP puts your nameservers in their DNS list for that specific set of IP adr. it should work fine.

ToastyX
04-21-2002, 04:14 PM
Originally posted by Asia
Is it normal when provider doesn't delegate you the
reverse zone, that's why you cant reverse resolve the IP. If you run:

nslookup ns1.gdznet.com ns1.gdznet.com
nslookup 66.220.13.162 ns1.gdznet.com


Does anyone have a clue how to fix this?

Is this a misconfigure in the box or the ISP side?

Yes, it is normal. Most providers won't delegate reverse DNS to you, BUT...it looks like in your case, your provider actually did give your server reverse DNS authority using a variation of classless in-addr.arpa delegation, so it looks like there's a misconfiguration on your server. You should be using the zone subnet160.13.220.66.in-addr.arpa, not 13.220.66.in-addr.arpa.

Fremont Servers
04-21-2002, 04:55 PM
This is the content of named.conf in FreeBSD 4.5

-----------------
> more named.conf
options {
directory "/etc/namedb";
auth-nxdomain yes;
recursion yes;
pid-file "/etc/namedb/named.pid";
dump-file "/etc/namedb/named-dump.db";
transfers-in 15;
transfers-per-ns 2;
};

logging {
channel config_log { file "/etc/namedb/log/config.log"; severity debug 5
; print-time yes; print-severity yes; print-category yes; };
channel db_log { file "/etc/namedb/log/db.log"; severity debug 5; print-
time yes; print-severity yes; print-category yes; };
channel eventlib_log { file "/etc/namedb/log/eventlib.log"; severity deb
ug 5; print-time yes; print-severity yes; print-category yes; };
channel load_log { file "/etc/namedb/log/load.log"; severity debug 5; pr
int-time yes; print-severity yes; print-category yes; };
channel maint_log { file "/etc/namedb/log/maint.log"; severity debug 5;
print-time yes; print-severity yes; print-category yes; };
channel misc_log { file "/etc/namedb/log/misc.log"; severity debug 5; pr
int-time yes; print-severity yes; print-category yes; };
named.conf 35%options {
directory "/etc/namedb";
auth-nxdomain yes;
recursion yes;
pid-file "/etc/namedb/named.pid";
dump-file "/etc/namedb/named-dump.db";
transfers-in 15;
transfers-per-ns 2;
};

logging {
channel config_log { file "/etc/namedb/log/config.log"; severity debug 5
; print-time yes; print-severity yes; print-category yes; };
channel db_log { file "/etc/namedb/log/db.log"; severity debug 5; print-
time yes; print-severity yes; print-category yes; };
channel eventlib_log { file "/etc/namedb/log/eventlib.log"; severity deb
ug 5; print-time yes; print-severity yes; print-category yes; };
channel load_log { file "/etc/namedb/log/load.log"; severity debug 5; pr
int-time yes; print-severity yes; print-category yes; };
channel maint_log { file "/etc/namedb/log/maint.log"; severity debug 5;
print-time yes; print-severity yes; print-category yes; };
channel misc_log { file "/etc/namedb/log/misc.log"; severity debug 5; pr
int-time yes; print-severity yes; print-category yes; };
channel notify_log { file "/etc/namedb/log/notify.log"; severity debug 5
; print-time yes; print-severity yes; print-category yes; };
channel packet_log { file "/etc/namedb/log/packet.log" size 10m versions
3; severity debug 5; print-time yes; print-severity yes; print-category yes; };
channel panic_log { file "/etc/namedb/log/panic.log"; severity debug 5;
print-time yes; print-severity yes; print-category yes; };
channel security_log { file "/etc/namedb/log/security.log"; severity deb
ug 5; print-time yes; print-severity yes; print-category yes; };
channel stats_log { file "/etc/namedb/log/stats.log"; severity debug 5;
print-time yes; print-severity yes; print-category yes; };
channel update_log { file "/etc/namedb/log/update.log"; severity debug 5
; print-time yes; print-severity yes; print-category yes; };
channel xfer_log { file "/etc/namedb/log/xfer.log"; severity debug 5; pr
int-time yes; print-severity yes; print-category yes; };
category cname { misc_log; };
category config { config_log; };
category db { db_log; };
category default { misc_log; };
category eventlib { eventlib_log; };
category insist { misc_log; };
category lame-servers { misc_log; };
category load { load_log; };
category maintenance { maint_log; };
category ncache { misc_log; };
category notify { notify_log; };
category os { misc_log; };
category packet { packet_log; };
category panic { panic_log; };
category parser { config_log; };
category response-checks { misc_log; };
category security { security_log; };
category statistics { stats_log; };
category update { notify_log; };
category xfer-in { xfer_log; };
category xfer-out { xfer_log; };
};


zone "." {
type hint;
file "named.root"; };

zone "gdznet.com" {
type master;
file "db.gdznet";
};

zone "13.220.66.in-addr.arpa" {
type master;
file "db.13.220.66";
};

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" {
type master;
file "localhost.rev";
};
------------------------

This is the content of db.gdznet file in FreeBSD 4.5

-----------------------
$TTL 3600
@ IN SOA ns1.gdznet.com. root.ns1.gdznet.com. (
2002042001 ; Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
604800 ; expire after 1 week
86400 ) ; Minimum TTL of one day

IN NS ns1.gdznet.com.
IN NS ns2.gdznet.com.


localhost IN A 127.0.0.1
ns1 IN A 66.220.13.162
ns2 IN A 66.220.13.163
irc IN A 66.220.13.164
guy IN A 66.220.13.165
jeff IN A 66.220.13.166
staff IN A 66.220.13.167
bum IN A 66.220.13.168
secure IN A 66.220.13.169
dns IN A 66.220.13.162
mail IN A 66.220.13.162
ftp IN A 66.220.13.162
www IN A 66.220.13.162
----------------------

This is the content of db.13.220.66 file in FreeBSD 4.5


--------------
$TTL 3600
@ IN SOA ns1.gdznet.com. root.ns1.gdznet.com. (
2002042001 ; Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
604800 ; expire after 1 week
86400 ) ; Minimum TTL of one day

IN NS ns1.gdznet.com.
IN NS ns2.gdznet.com.

162 IN PTR ns1.gdznet.com.
163 IN PTR ns2.gdznet.com.
164 IN PTR irc.gdznet.com.
165 IN PTR guy.gdznet.com.
166 IN PTR jeff.gdznet.com.
167 IN PTR staff.gdznet.com.
168 IN PTR bum.gdznet.com.
169 IN PTR secure.gdznet.com.
---------------------------

This is the content of localhost.rev file in FreeBSD 4.5

--------------------------
$TTL 3600
@ IN SOA ns1.gdznet.com. root.ns1.gdznet.com. (
2002042000 ; Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
604800 ; expire after 1 week
86400 ) ; Minimum TTL of one day

IN NS ns1.gdznet.com.
IN NS ns2.gdznet.com.

1 IN PTR localhost.gdznet.com.
---------------------------



Do you see any misconfiguration to the above named.conf, db.gdznet, db.13.220.66, and localhost.rev?

Fremont Servers
04-21-2002, 05:10 PM
Yes, it is normal. Most providers won't delegate reverse DNS to you, BUT...it looks like in your case, your provider actually did give your server reverse DNS authority using a variation of classless in-addr.arpa delegation, so it looks like there's a misconfiguration on your server. You should be using the zone subnet160.13.220.66.in-addr.arpa, not 13.220.66.in-addr.arpa.


ToastyX,

I tried your method and it worked.
Thank you very much for your help.

I'd like to thank dot.K and others for helping me out.