大网数据广告活动
服务器运维问答

PowerDNS Recursor for Reverse Zones

· 52CE 我爱测

I'm trying to deploy some PowerDNS servers as an internal DNS host, and I've got the recursor working, and the authoritative working, but the only thing I don't have functional is the reverse lookups. The system is configured to …

问题原文

原帖链接 · DavisTasar · CC BY-SA 4.0

I'm trying to deploy some PowerDNS servers as an internal DNS host, and I've got the recursor working, and the authoritative working, but the only thing I don't have functional is the reverse lookups. The system is configured to run in the Native setup, with MySQL as the backend.

The Recursor and the Authoritative are running on the same box. Recursor is listening on udp/53, and is set to forward requests for the appropriate domains to the authoritative running on udp/5300. I have a forward setup for the internal company name (internal.corp as the example below), so the A Records, CNAMES, etc., all work as appropriate. The problem I run into is the reverse zones.

I've tried doing:

forward-zones+=139.10.in-addr.arpa=127.0.0.1:5300

forward-zones+=0.139.10.in-addr.arpa=127.0.0.1:5300

forward-zones+=0.0.139.10.in-addr.arpa=127.0.0.1:5300

Hell, I even tried a specific entry:

forward-zones+=10.0.139.10.in-addr.arpa=127.0.0.1:5300

And no joy. So, if anyone has a suggestion on how I should poke it, I'd appreciate it!

Configs below:

#power dns authoritative
launch=gmysql
gmysql-host=127.0.0.1
gmysql-user=root
gmysql-dbname=pdns
gmysql-password=thisismysuperawesomepassword
webserver=yes
webserver-address=0.0.0.0
api=yes
api-key=changeme
local-ipv6=
local-address=127.0.0.1
local-port=5300


--------
#powerdns recursor
setgid=pdns-recursor
setuid=pdns-recursor
local-address=0.0.0.0
webserver=yes
webserver-port=8082
api-key=changeme
forward-zones=example.com=127.0.0.1:5300
forward-zones+=internal.corp=127.0.0.1:5300

已采纳解答

原帖链接 · George Ivanov · CC BY-SA 4.0

I have similar setup. Auth and recurosor 4.2.x version Forward zone (example.com) and reverse zone (in-addr.apra) defined on authoritative server. What helped me was adding serve-rfc1918=no on recursor's config. Thus recursor actually forwards reverse requests to authoritative server.

Recursor's related config:

forward-zones=example.com=127.0.0.1:5300, in-addr.arpa=127.0.0.1:5300
serve-rfc1918=no

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-07-22)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。