re 2 -- I believe I have set the host entry for ns1.yyrrll.net in the GoDaddy host panel, for that name and the linode IP address. Do you mean to set the hostname and IP address for the linode serving as host for ns1.yyrrll.net?
db.yyrrll.net:
Code:
$TTL 3600
yyrrll.net. IN SOA ns1.yyrrll.net. webmaster.yyrrll.net. (
201202221254 ; Serial
3600 ; Refresh [1h]
600 ; Retry [10m]
86400 ; Expire [1d]
600 ) ; Negative Cache TTL [1h]
;
; Name servers
yyrrll.net. IN NS ns1.yyrrll.net.
yyrrll.net. IN NS ns1.linode.com.
; Glue records for name servers
ns1.yyrrll.net. IN A 66.228.58.59
; Mail records
yyrrll.net. IN MX 10 mail.yyrrll.net.
yyrrll.net. IN TXT "v=spf1 +a:mail.yyrrll.net -all"
; Loopback
localhost.yyrrll.net. IN A 127.0.0.1
; Host records
yyrrll.net. IN A 66.228.58.59
cheshire.yyrrll.net. IN A 66.228.58.59
mail.yyrrll.net. IN A 66.228.58.59
; Aliases
www IN CNAME yyrrll.net.
named.conf:
Code:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
// From wiki.debian.org/Bind9
// Managing acls
acl internals { 127.0.0.0/8; 192.168.0.0/24; };
// Load options
include "/etc/bind/named.conf.options";
// TSIG key used for the dynamic update
include "/etc/bind/ns-yyrrll-net_rndc-key";
// Configure the communication channel for Administrative BIND9 with rndc
// By default, they key is in the rndc.key file and is used by rndc and bind9
// on the localhost
controls {
inet 127.0.0.1 port 953 allow { 127.0.0.1; };
};
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
include "/etc/bind/named.conf.local";
// Not in Debian example configuration but was present in .initial:
//-include "/etc/bind/named.conf.default-zones";
named.conf.local::
Code:
// Manage the file logs
include "/etc/bind/named.conf.log";
// Domain Management example.com
// ------------------------------
// - The server is defined as the master on the domain.
// - There are no forwarders for this domain.
// - Entries in the domain can be added dynamically
// with the key ns-example-com_rndc-key
// Configuration for yyrrll.net
zone "yyrrll.net" {
type master;
file "/etc/bind/db.yyrrll.net";
//-err?-file "/var/cache/bind/db.yyrrll.net";
//forwarders {};
// If we do not comment the ''forwarders'' "empty" clients of the local subnet in my case don't have access to the upstream DNS ?
//allow-update { key ns-yyrrll-net_rndc-key; };
allow-update { key rndc-key; };
//confusion between the file name to import (ns-example-com_rndc-key) and the key label (rndc-key) ?
};
zone "59.58.228.66.in-addr.arpa" {
type master;
file "/etc/bind/db.59.58.228.66";
//-err?-file "/var/cache/bind/db.59.58.228.66";
//see comment below (zone "example.com")
//forwarders {};
//allow-update { key ns-yyrrll-net_rndc-key; };
allow-update { key rndc-key; };
};
// Consider adding the 1918 zones here, if they are not used in your
// organization
include "/etc/bind/zones.rfc1918";
Thank you for looking at this.
EDIT: possibly relevant detail:
- the linode has hostname 'cheshire', which is not in the GoDaddy host designation at this writing (I'm going to add it after this)
- bind9 is running under chroot; /etc/default/bind9 includes << OPTIONS="-u bind -t /var/bind/chroot" >>
FAQ
Search
Members
Register
Login [ Anonymous ]
