DNS伺服器不能反向解析
操作系統: SUSE LINUX 10
問題:DNS伺服器不能反向解析,謝謝各位大俠分析
解析過程如下:
> dns1:/var/lib/named/master # nslookup
> dns1
Server: 10.54.210.1
Address: 10.54.210.1#53
Name: dns1.xz.earthquake.cn
Address: 10.54.210.1
> dns1.xz.earthquake.cn
Server: 10.54.210.1
Address: 10.54.210.1#53
Name: dns1.xz.earthquake.cn
Address: 10.54.210.1
> 10.54.210.1
Server: 10.54.210.1
Address: 10.54.210.1#53
*** Can't find 1.210.54.10.in-addr.arpa.: No answer
> dbser1
Server: 10.54.210.1
Address: 10.54.210.1#53
Name: dbser1.xz.earthquake.cn
Address: 10.54.201.1
> dbser1.xz.earthquake.cn
Server: 10.54.210.1
Address: 10.54.210.1#53
Name: dbser1.xz.earthquake.cn
Address: 10.54.201.1
> 10.54.201.1
Server: 10.54.210.1
Address: 10.54.210.1#53
*** Can't find 1.201.54.10.in-addr.arpa.: No answer
named.conf配置文件如下:
# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9. It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.
options {
# The directory statement defines the name server's working directory
directory "/var/lib/named";
# Write dump and statistics file to the log subdirectory. The
# pathenames are relative to the chroot jail.
dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";
# The forwarders record contains a list of servers to which queries
# should be forwarded. Enable this line and modify the IP address to
# your provider's name server. Up to three servers may be listed.
#forwarders { 192.0.2.1; 192.0.2.2; };
# Enable the next entry to prefer usage of the name server declared in
# the forwarders section.
#forward first;
# The listen-on record contains a list of local network interfaces to
# listen on. Optionally the port can be specified. Default is to
# listen on all interfaces found on your system. The default port is
# 53.
#listen-on port 53 { 127.0.0.1; };
# The listen-on-v6 record enables or disables listening on IPv6
# interfaces. Allowed values are 'any' and 'none' or a list of
# addresses.
listen-on-v6 { any; };
# The next three statements may be needed if a firewall stands between
# the local server and the internet.
#query-source address * port 53;
#transfer-source * port 53;
#notify-source * port 53;
# The allow-query record contains a list of networks or IP addresses
# to accept and deny queries from. The default is to allow queries
# from all hosts.
#allow-query { 127.0.0.1; };
# If notify is set to yes (default), notify messages are sent to other
# name servers when the the zone data is changed. Instead of setting
# a global 'notify' statement in the 'options' section, a separate
# 'notify' can be added to each zone definition.
notify no;
include "/etc/named.d/forwarders.conf";
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};
# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.
zone "." in {
type hint;
file "root.hint";
};
zone "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
# Include the meta include file generated by createNamedConfInclude. This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named
include "/etc/named.conf.include";
zone "xz.earthquake.cn" IN {
file "master/xz.earthquake.cn";
type master;
};
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
};
acl dns1 { 10.54.210.1; };
zone "210.54.10.in-addr.arpa" IN {
file "master/210.54.10.in-addr.arpa";
type master;
};
zone "201.54.10.in-addr.arpa" IN {
file "master/201.54.10.in-addr.arpa";
type master;
};
# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
xa.earthquake.cn文件內容如下:
$TTL 2d
@ IN SOA dns1.xz.earthquake.cn. root.dns1.xz.earthquake.cn. (
2007053101 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
IN NS dns1.xz.earthquake.cn.
dns1 IN A 10.54.210.1
dns2 IN A 10.54.210.2
dbser1 IN A 10.54.201.1
dbser2 IN A 10.54.201.2
210.54.10.in-addr.arpa文件內容如下:
$TTL 2d
@ IN SOA dns1.xz.earthquake.cn. root.xz.earthquake.cn. (
2007053102 ; serial
3h ; refresh
1h ; retry
1w ; expiry
1d ) ; minimum
IN NS dns1.xz.earthquake.cn.
10.54.210.1 IN PTR dns1.xz.earthquake.cn.
10.54.210.2 IN PTR dns2.xz.earthquake.cn.
201.54.10.in-addr.arpa文件內容如下:
$TTL 2D
@ IN SOA dns1.xz.earthquake.cn. root.dns1.xz.earthquake.cn. (
2007053100 ; serial
3H ; refresh
1H ; retry
1W ; expiry
1D ) ; minimum
10.54.201.1 IN PTR dbser1.xz.earthquake.cn.
10.54.201.2 IN PTR dbser2.xz.earthquake.cn.
[ 本帖最後由 jlhwlw 於 2007-5-31 17:25 編輯 ]
《解決方案》
格式很差呢
以後要用CODE
而且DNS的格式是很重要的
PTR那裡
怎麼會有兩份呢
是發錯了嗎？
《解決方案》
回復 2樓 vyouzhi 的帖子
上面寫錯了文件名,已經更改了。麻煩各位大俠再幫我看看,無論怎樣都無法把地址解析出來.謝謝各位
《解決方案》
10.54.201.1 IN PTR dbser1.xz.earthquake.cn.
10.54.201.2 IN PTR dbser2.xz.earthquake.cn.
改成
1 IN PTR dbser1.xz.earthquake.cn.
2 IN PTR dbser2.xz.earthquake.cn.
《解決方案》
我是有幾個網段呢?如果改為
1 IN PTR dbser1.xz.earthquake.cn.
2 IN PTR dbser2.xz.earthquake.cn.
可以嗎?
《解決方案》
原帖由 jlhwlw 於 2007-5-31 18:14 發表
我是有幾個網段呢?如果改為
1 IN PTR dbser1.xz.earthquake.cn.
2 IN PTR dbser2.xz.earthquake.cn.
可以嗎?
zone "210.54.10.in-addr.arpa" IN {
file "master/210.54.10.in-addr.arpa";
type master;
};
zone "201.54.10.in-addr.arpa" IN {
file "master/201.54.10.in-addr.arpa";
type master;
};
不同網段有不同記錄檔, 不是嗎?
建議您參考 網大 的文章, 複習一下設定方式,
網址如下 : http://www.study-area.org/linux/servers/linux_dns.htm
:P
《解決方案》
不同網段有不同記錄檔這個我已經設置了,但不知道為什麼不能反向解析
《解決方案》
公網IP的反向解析應該不會跑到你的伺服器來的。
那個需要ip提供單位做的
《解決方案》
而且做這個反向解析要收費的
《解決方案》
我現在是在內網建立多網段的DNS伺服器,並不需要外部來解析呀.可不知道為什麼不能反向解析,麻煩各位大俠在分析問題可能出在那裡.
