Looking for a pointer on getting reverse mapping with DDNS to work with DHCPD & Named.
Jim Bucks
jbucks at coloradostudios.com
Tue Mar 26 14:28:38 UTC 2013
Problem.
===============================================================
I'm working on getting a DHCP / Bind / DDNS server set up. When a client
receives
an IP address "lease", I want the forward / reverese "zones" files updated
so
name lookups behave appropriately / as expected.
After a couple of days of fiddling with this (and lots of Google / ISC
searches), I'm
still unable to get the IP address lease for a workstation to be
auto-entered into
my reverse db.dhcp.coloradostudios.com "zones" file.
I'm getting either of the following errors:
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to
proccilapxp.dhcp.coloradostudios.com: bad DNS key
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to
proccilapxp.dhcp.coloradostudios.com: timed out
It apparently has something to do with how I'm using the "keys" to tell /
let dhcpd
update the DNS "zones" file, but I'll be 'derned if I can figure out what's
breaking.
Any pointers on what to look for in order to get this working would be
appreciated.
Thanks,
Jim
I've attached the current configs in the hopes this is merely a simple
syntactical error on my part.
--
Jim Bucks - IT Director
Colorado Studios <http://www.coloradostudios.com>, Mobile TV
Group<http://www.mobiletvgroup.com>,
HDNet <http://www.hd.net>, AXS.tv <http://www.axs.tv/>
8269 E. 23rd Ave. Denver, CO 80238 Main 303-388-8500
jbucks at coloradostudios.com Direct 303-542-5520
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130326/4a4df206/attachment.html>
-------------- next part --------------
Centos 64 bit ver 6.4
dhcpd ver 4.1.1-P1
bind var BIND 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6.3
All the above are on one server.
Problem.
===============================================================
I'm working on getting a DHCP / Bind / DDNS server set up. When a client receives
an IP address "lease", I want the forward / reverese "zones" files updated so
name lookups behave appropriately / as expected.
After a couple of days of fiddling with this (and lots of Google / ISC searches), I'm
still unable to get the IP address lease for a workstation to be auto-entered into
my reverse db.dhcp.coloradostudios.com "zones" file.
I'm getting either of the following errors:
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to proccilapxp.dhcp.coloradostudios.com: bad DNS key
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to proccilapxp.dhcp.coloradostudios.com: timed out
It apparently has something to do with how I'm using the "keys" to tell / let dhcpd
update the DNS "zones" file, but I'll be 'derned if I can figure out what's breaking.
Any pointers on what to look for in order to get this working would be appreciated.
Thanks,
Jim
Here are all my configuration & logfiles. They are 99% the same as my "real" files.
The only change was to replace the "secret" string. Syntactically, there are no changes.
cat /etc/dhcp/dhcpd.conf
==============================================================
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
# Sept 19, 2012 jbucks
# /etc/dhcp/dhcdp.conf file - prepping for dhcp rollout
#
#
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# # Separate multiple interfaces with spaces, e.g. "eth0 eth1".>
INTERFACES="eth1";
# Use this to send dhcp log messages to a different log file (you also
# # have to hack syslog.conf to complete the redirection).
log-facility local6;
authoritative; # Sets the server authoritative for my network
ddns-update-style interim; # Activates Dynamic DNS
update-static-leases-on; # Ensures static leases get entered
#ignore client-updates;
# Use this command line to generate the key. Only need the key string inside these files.
# dnssec-keygen -a HMAC-MD5 -b 128 -n USER DHCP_UPDATER
#
# It is very important to use the exact same keystring and name on both dhcpd.conf and named.conf for this to work.
key DHCP_UPDATER { # This line specifies the key name
# algorithm HMAC-MD5.SIG-ALG.REG.INT; # This line specifies the encryption algorithm best to stick with HMAC-MD5
algorithm HMAC-MD5; # This line specifies the encryption algorithm best to stick with HMAC-MD5
secret x99yzTXeeeeeOPQLKsd==; # Finally the key statement itself
};
subnet 172.10.0.0 netmask 255.255.0.0 {
# --- default gateway
option routers 172.10.5.1;
option subnet-mask 255.255.0.0;
option nis-domain "coloradostudios.com";
option domain-name "coloradostudios.com";
option domain-name-servers 172.10.5.5;
option time-offset -25200; # Mountain Standard Time
# option time-offset -18000; # Eastern Standard Time
# option ntp-servers 192.168.1.1;
# option netbios-name-servers 192.168.1.1;
# --- Selects point-to-point node (default is hybrid). Don't change this unless
# -- you understand Netbios very well
# option netbios-node-type 2;
# range dynamic-bootp 172.10.20.51 172.10.21.254;
range 172.10.20.51 172.10.21.254;
default-lease-time 21600;
max-lease-time 43200;
# include "/var/named/chroot/Kdhcp_updater.+157+32728.key";
# These zones statements are part of the dynamic dns (named) as they link back into the bind (named) zones
zone dhcp.coloradostudios.com. {
primary db.dhcp.coloradostudios.com;
key DHCP_UPDATER;
#file "internal/db.dhcp.coloradostudios.com";
}
zone 20.10.172.in-addr.arpa. {
primary db.172.10.20.;
key DHCP_UPDATER;
#file "internal/db.172.10.20";
}
# we want the nameserver to appear at a fixed address
# host ns {
# next-server marvin.redhat.com;
# hardware ethernet 12:34:56:78:AB:CD;
# fixed-address 207.175.42.254;
# }
}
cat /var/named/chroot/etc/named.conf
==================================================================
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// 2013 Feb 13 jbucks - initial setup for new House Lan IP Range and DHCP setup.
//
// This is a list of the Stapleton Hosts
acl stapleton_hosts {
127.0.0.1;
172.10.0/16;
};
options {
listen-on port 53 { 127.0.0.1 ; 172.10.0.0; };
// listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
zone-statistics yes;
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
// allow-query { localhost; };
allow-query { stapleton_hosts; };
recursion yes;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
# bindkeys-file "/etc/named.iscdlv.key";
# managed-keys-directory "/var/named/dynamic";
version "secret";
key-directory "/etc/keys";
};
# Use this command line to generate the key. Only need the key string inside these files.
# dnssec-keygen -a HMAC-MD5 -b 128 -n USER DHCP_UPDATER
#
# It is very important to use the exact same keystring and name on both dhcpd.conf and named.conf for this to work.
key DHCP_UPDATER { # This line specifies the key name
# algorithm HMAC-MD5.SIG-ALG.REG.INT; # This line specifies the encryption algorithm best to stick with HMAC-MD5
algorithm HMAC-MD5; # This line specifies the encryption algorithm best to stick with HMAC-MD5
secret x99yzTXeeeeeOPQLKsd==; # Finally the key statement itself
};
logging {
channel default_file {
file "/var/log/named/named.log" size 10m;
severity debug;
print-time yes;
print-severity yes;
print-category yes;
};
category default{ default_file; };
channel default_debug {
# file "data/named.run";
file "/var/log/named/bind.log" versions 5 size 5m;
severity dynamic;
# severity debug;
print-time yes;
print-category yes;
print-severity yes;
};
// Filter out any LAME server messages from cluttering up the SYSLOGs
category lame-servers { null; };
// category dnssec { null; };
// record all the zone transfer requests in an easy to read file.
channel log_zone_transfers {
# file "data/axfr.log" versions 10 size 20m;
file "/var/log/named/axfr.log" versions 10 size 20m;
print-time yes;
print-category yes;
print-severity yes;
};
category xfer-out { log_zone_transfers; };
channel query_logging {
#file "data/querylog" versions 10 size 100M;
file "/var/log/named/querylog" versions 10 size 100M;
print-time yes; // timestamp log entries
print-category yes;
print-severity yes;
};
category queries { query_logging; };
channel update_debug {
file "/var/log/named/update-debug.log";
severity debug 3;
print-category yes;
print-severity yes;
print-time yes;
};
channel security_info {
file "/var/log/named/named-auth.info";
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
category update { update_debug; };
category security { security_info; };
};
//zone "." IN {
// type hint;
// file "named.ca";
//};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
view localhost_resolver {
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
# all views must contain the root hints zone:
//include "/etc/named.root.hints";
//include "/var/named/chroot/etc/named.root.hints";
/* these are zones that contain definitions for all the localhost
* names and addresses, as recommended in RFC1912 - these names should
* ONLY be served to localhost clients:
*/
//include "internal/named.rfc1912.zones";
};
view internal {
/* This view will contain zones you want to serve only to "internal" clients
* that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { 172.10.0.0/16; };
match-destinations { 172.10.0.0/16; };
recursion yes;
zone "." {
type hint;
file "internal/root.hints";
};
// all views must contain the root hints zone:
//include "internal/root.hints";
//include "internal/named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.
// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :
// New - Post March 2013 House Lan - Servers
zone "5.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.5";
};
// New - Post March 2013 House Lan - Server Managment
zone "7.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.7";
};
// New - Post March 2013 House Lan - Switches
zone "10.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.10";
};
// New - Post March 2013 House Lan - Printers
zone "12.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.12";
};
// New - Post March 2013 House Lan - Unclassified
zone "15.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.15";
};
// New - Post March 2013 House Lan - Mission Critical
zone "17.10.172.in-addr.arpa" {
type master;
allow-transfer { 172.20.24.103; };
file "internal/db.172.10.17";
};
// New - Post March 2013 House Lan - DHCP
// 172.10.20.0 - 172.10.21.255
# These zones statements are part of the dynamic dns (named) as they link back into the bind (named) zones
# forward
zone "dhcp.coloradostudios.com" {
type master;
file "internal/db.dhcp.coloradostudios.com";
allow-update{ key DHCP_UPDATER; };
allow-query {
172.10.5.5/16;
};
};
# reverse
zone "20.10.172.in-addr.arpa" {
type master;
file "internal/db.172.10.20";
allow-update{ key DHCP_UPDATER; };
allow-query {
172.10.5.5/16;
};
};
// //zone "my.internal.zone" {
// type master;
// file "my.internal.zone.db";
// };
// zone "my.slave.internal.zone" {
// type slave;
// file "slaves/my.slave.internal.zone.db";
// masters { /* put master nameserver IPs here */ 127.0.0.1; };
// // put slave zones in the slaves/ directory so named can update them
// };
// zone "my.ddns.internal.zone" {
// type master;
// allow-update { key ddns_key; };
// file "slaves/my.ddns.internal.zone.db";
// // put dynamically updateable zones in the slaves/ directory so named can update them
// };
};
key rndc_key
{
algorithm hmac-md5;
secret "K40Ow3lmPHFgOAR1uFl9hCLLhD2Eb9ZixW/27Ss0eaomlasl7ikice/G8doz1NbE3vtwudf52nNRhFiQR8PxCw==";
};
key ddns_key
{
algorithm hmac-md5;
secret "OOIMuD4OSVH1IXVV769nw2sjPd3gVUKiL8zq3lh3XJlAVMiTPYhs6vwk5BXo";
//secret "use /usr/sbin/dns-keygen to generate TSIG keys";
};
view external
{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
recursion no;
// you'd probably want to deny recursion to external clients, so you don't
// end up providing free DNS service to all takers
// all views must contain the root hints zone:
//include "/etc/named.root.hints";
// zone "my.external.zone" {
// type master;
// file "my.external.zone.db";
// };
};
//include "/etc/named.rfc1912.zones";
//include "/etc/named.root.key";
DNS "Zones" files.
==================================================================
cat /var/named/chroot/var/named/internal/db.dhcp.coloradostudios.com
$TTL 1d
dhcp.coloradostudios.com. IN SOA dns04.coloradostudios.com. sysmgr.axs.tv. (
2013032601 ;Serial use this format yyyymmddvv where vv is that days version number
10800 ;Refresh after 3 hours
3600 ;Retry after 1 hour
604800 ;Expire after 1 week
86400 ) ;Min TTL of 1 day
;
; This is for the Internal Stapleton machines for Colorado Studios
;
;
; Name Servers
;
dhcp.coloradostudios.com. IN NS dns04.coloradostudios.com.
DHCP_UPDATER. IN KEY 0 3 157 x99yzTXeeeeeOPQLKsd==
------------------------------------------------------------------
cat /var/named/chroot/var/named/internal/db.172.10.20
$TTL 1d
20.10.172.in-addr.arpa. IN SOA dns04.coloradostudios.com. sysmgr.hd.net. (
2013022600 ; Serial
10800 ;Refresh after 3 hours
3600 ;Retry after 1 hour
604800 ;Expire after 1 week
86400 ) ;Min TTL of 1 day
; Name Servers
20.10.172.in-addr.arpa. IN NS dns04.den.coloradostudios.com.
------------------------------------------------------------------
cat /var/lib/dhcpd/dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.1.1-P1
lease 172.10.20.53 {
starts 4 2013/03/21 19:38:17;
ends 5 2013/03/22 01:38:17;
tstp 5 2013/03/22 01:38:17;
cltt 4 2013/03/21 19:38:17;
binding state free;
hardware ethernet 5c:ac:4c:99:be:b8;
uid "\001\\\254L\231\276\270";
}
lease 172.10.20.52 {
starts 4 2013/03/21 19:38:23;
ends 5 2013/03/22 01:38:23;
tstp 5 2013/03/22 01:38:23;
cltt 4 2013/03/21 19:38:23;
binding state free;
hardware ethernet 60:eb:69:25:6a:13;
uid "\001`\353i%j\023";
}
lease 172.10.20.51 {
starts 2 2013/03/26 13:02:37;
ends 2 2013/03/26 19:02:37;
tstp 2 2013/03/26 19:02:37;
cltt 2 2013/03/26 13:02:37;
binding state active;
next binding state free;
hardware ethernet 00:0b:cd:33:b6:49;
uid "\001\000\013\3153\266I";
client-hostname "proccilapxp";
}
server-duid "\000\001\000\001\030\333@\376\\\363\374'\005U";
lease 172.10.20.51 {
starts 2 2013/03/26 13:02:37;
ends 2 2013/03/26 13:17:12;
tstp 2 2013/03/26 13:17:12;
cltt 2 2013/03/26 13:02:37;
binding state free;
hardware ethernet 00:0b:cd:33:b6:49;
uid "\001\000\013\3153\266I";
}
lease 172.10.20.51 {
starts 2 2013/03/26 13:17:23;
ends 2 2013/03/26 19:17:23;
cltt 2 2013/03/26 13:17:23;
binding state active;
next binding state free;
hardware ethernet 00:0b:cd:33:b6:49;
uid "\001\000\013\3153\266I";
client-hostname "proccilapxp";
}
File Permissions & Ownerships
=================================================================
ll /var/named/chroot/var/named/internal/db.dhcp.coloradostudios.com
-rw-rw-rw- 1 named named 579 Mar 26 07:14 db.dhcp.coloradostudios.com
ll /var/named/chroot/var/named/internal/db.172.10.20
-rw-rw-rw- 1 named named 386 Mar 21 08:18 db.172.10.20
ll /var/lib/dhcpd/dhcpd.leases
-rw-r--r-- 1 root root 1469 Mar 26 07:17 /var/lib/dhcpd/dhcpd.leases
ll /etc/dhcp/dhcpd.conf
-rw-r--r-- 1 root root 2898 Mar 26 07:16 /etc/dhcp/dhcpd.conf
ll /var/named/chroot/etc/named.conf
-rw-r----- 1 root named 9608 Mar 26 07:12 /var/named/chroot/etc/named.conf
/var/log/messages file
=================================================================
Restarted dhcpd & named deamons....
Mar 26 07:16:49 dns04 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 26 07:16:49 dns04 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 26 07:16:49 dns04 dhcpd: All rights reserved.
Mar 26 07:16:49 dns04 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 26 07:16:49 dns04 dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Mar 26 07:16:49 dns04 dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar 26 07:16:49 dns04 dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar 26 07:16:49 dns04 dhcpd: All rights reserved.
Mar 26 07:16:49 dns04 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar 26 07:16:49 dns04 dhcpd: Wrote 3 leases to leases file.
Mar 26 07:16:49 dns04 dhcpd: Listening on LPF/eth1/5c:f3:fc:27:05:55/172.10.0.0/16
Mar 26 07:16:49 dns04 dhcpd: Sending on LPF/eth1/5c:f3:fc:27:05:55/172.10.0.0/16
Mar 26 07:16:49 dns04 dhcpd: Sending on Socket/fallback/fallback-net
Mar 26 07:16:59 dns04 named-sdb[26873]: starting BIND 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6.3 -u named -t /var/named/chroot
Mar 26 07:16:59 dns04 named-sdb[26873]: built with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--target=x86_64-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-libtool' '--localstatedir=/var' '--enable-threads' '--enable-ipv6' '--with-pic' '--disable-static' '--disable-openssl-version-check' '--with-dlz-ldap=yes' '--with-dlz-postgres=yes' '--with-dlz-mysql=yes' '--with-dlz-filesystem=yes' '--with-gssapi=yes' '--disable-isc-spnego' '--with-docbook-xsl=/usr/share/sgml/docbook/xsl-stylesheets' '--enable-fixed-rrset' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'target_alias=x86_64-redhat-linux-gnu' 'CFLAGS= -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' 'CPPFLAGS= -DDIG_SIGCHASE'
Mar 26 07:16:59 dns04 named-sdb[26873]: ----------------------------------------------------
Mar 26 07:16:59 dns04 named-sdb[26873]: BIND 9 is maintained by Internet Systems Consortium,
Mar 26 07:16:59 dns04 named-sdb[26873]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Mar 26 07:16:59 dns04 named-sdb[26873]: corporation. Support and training for BIND 9 are
Mar 26 07:16:59 dns04 named-sdb[26873]: available at https://www.isc.org/support
Mar 26 07:16:59 dns04 named-sdb[26873]: ----------------------------------------------------
Mar 26 07:16:59 dns04 named-sdb[26873]: adjusted limit on open files from 4096 to 1048576
Mar 26 07:16:59 dns04 named-sdb[26873]: found 4 CPUs, using 4 worker threads
Mar 26 07:16:59 dns04 named-sdb[26873]: using up to 4096 sockets
Mar 26 07:16:59 dns04 named-sdb[26873]: SDB ldap zone database module loaded.
Mar 26 07:16:59 dns04 named-sdb[26873]: SDB postgreSQL DB zone database module loaded.
Mar 26 07:16:59 dns04 named-sdb[26873]: SDB sqlite3 DB zone database module loaded.
Mar 26 07:16:59 dns04 named-sdb[26873]: SDB directory DB zone database module loaded.
Mar 26 07:16:59 dns04 named-sdb[26873]: loading configuration from '/etc/named.conf'
Mar 26 07:16:59 dns04 named-sdb[26873]: using default UDP/IPv4 port range: [1024, 65535]
Mar 26 07:16:59 dns04 named-sdb[26873]: using default UDP/IPv6 port range: [1024, 65535]
Mar 26 07:16:59 dns04 named-sdb[26873]: listening on IPv4 interface lo, 127.0.0.1#53
Mar 26 07:16:59 dns04 named-sdb[26873]: generating session key for dynamic DNS
Mar 26 07:16:59 dns04 named-sdb[26873]: sizing zone task pool based on 9 zones
Mar 26 07:16:59 dns04 named-sdb[26873]: using built-in DLV key for view localhost_resolver
Mar 26 07:16:59 dns04 named-sdb[26873]: set up managed keys zone for view localhost_resolver, file 'dynamic/03641f096ea0ceb02e407a63ea6d9e42d7ceafabd8156336551aeae23ee060ed.mkeys'
Mar 26 07:16:59 dns04 named-sdb[26873]: Warning: view localhost_resolver: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 0.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 127.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 254.169.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 2.0.192.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 100.51.198.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 113.0.203.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 255.255.255.255.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 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.0.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 1.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.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: D.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 8.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 9.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: A.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: B.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view localhost_resolver: 8.B.D.0.1.0.0.2.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: using built-in DLV key for view internal
Mar 26 07:16:59 dns04 named-sdb[26873]: set up managed keys zone for view internal, file 'dynamic/3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys'
Mar 26 07:16:59 dns04 named-sdb[26873]: Warning: view internal: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 0.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 127.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 254.169.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 2.0.192.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 100.51.198.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 113.0.203.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 255.255.255.255.IN-ADDR.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 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.0.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 1.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.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: D.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 8.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 9.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: A.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: B.E.F.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: automatic empty zone: view internal: 8.B.D.0.1.0.0.2.IP6.ARPA
Mar 26 07:16:59 dns04 named-sdb[26873]: using built-in DLV key for view external
Mar 26 07:16:59 dns04 named-sdb[26873]: set up managed keys zone for view external, file 'dynamic/3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys'
Mar 26 07:16:59 dns04 named-sdb[26873]: command channel listening on 127.0.0.1#953
Mar 26 07:16:59 dns04 named-sdb[26873]: command channel listening on ::1#953
On the Windows Workstation, did a release & renew ....
Mar 26 07:17:12 dns04 dhcpd: DHCPRELEASE of 172.10.20.51 from 00:0b:cd:33:b6:49 (proccilapxp) via eth1 (found)
Mar 26 07:17:22 dns04 dhcpd: DHCPDISCOVER from 00:0b:cd:33:b6:49 via eth1
Mar 26 07:17:23 dns04 dhcpd: DHCPOFFER on 172.10.20.51 to 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 26 07:17:23 dns04 dhcpd: db.172.10.20.: host unknown.
Mar 26 07:17:25 dns04 dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to proccilapxp.dhcp.coloradostudios.com: timed out
Mar 26 07:17:25 dns04 dhcpd: DHCPREQUEST for 172.10.20.51 (172.10.5.5) from 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 26 07:17:25 dns04 dhcpd: DHCPACK on 172.10.20.51 to 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 26 07:24:06 dns04 avahi-daemon[1601]: Invalid query packet.
Mar 26 07:24:06 dns04 avahi-daemon[1601]: Invalid query packet.
OR------
Mar 26 07:56:51 dns04 dhcpd: DHCPRELEASE of 172.10.20.51 from 00:0b:cd:33:b6:49 (proccilapxp) via eth1 (found)
Mar 26 07:56:58 dns04 dhcpd: DHCPDISCOVER from 00:0b:cd:33:b6:49 via eth1
Mar 26 07:56:59 dns04 dhcpd: DHCPOFFER on 172.10.20.51 to 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 26 07:56:59 dns04 dhcpd: db.172.10.20.: host unknown.
Mar 26 07:56:59 dns04 dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to proccilapxp.dhcp.coloradostudios.com: bad DNS key
Mar 26 07:56:59 dns04 dhcpd: DHCPREQUEST for 172.10.20.51 (172.10.5.5) from 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 26 07:56:59 dns04 dhcpd: DHCPACK on 172.10.20.51 to 00:0b:cd:33:b6:49 (proccilapxp) via eth1
More information about the bind-users
mailing list