DNS problems - unstable domain - no glue
Kenneth Andresen
kandresen at gmx.net
Wed Jul 14 22:07:01 UTC 2004
Hello all,
I have been trying to get two domains working for some time now, but it
seems to be highly unstable - some times I find the address correctly,
other times I don't... The old server used bind 8, the new one uses bind
9.2.2.
One of the domains use its own subdomain as primary DNS server, I am
considering if this might be where the problem is(?) I am also noting
that the reversed lookup of the domain ip returns domaintwo.com, not
domainone.com in arpa.
Using dns report I have get the following warnings and error messages:
Domain1.com:
Parent: Warn: NS records at parent servers: ns2.extns.com. (OK)
ns1.domainone.com. [NO GLUE; No A record]
Parent: Warn: Glue at parent nameservers : Warning NO GLUE at root
server for domain1.com
NS: FAIL: Missing nameservers: Problem NS records: ns1.domainone.com.
Domaintwo.com:
Parent: Warn: Glue at parent nameservers : [NO GLUE; No A record]
NS: FAIL: All NS IPs public: The problem ips are "is not a public ip"
Divided by ------- lines, I have added /etc/named.conf,
/var/named/domain1.com.zone, /var/named/domain2.com.zone, and
/var/named/domain1.com-reversed.zone in that order. :
------------- /etc/named.conf
options {
directory "/var/named";
// query-source address * port 53;
version "You have to guess it!";
pid-file "/var/run/named/named.pid";
// minimal responses, improve performance
minimal-responses 1;
// do not provide additional info from cache
# additional-from-cache no;
};
logging {
channel my_syslog {
syslog daemon;
severity info;
};
channel my_file {
file "named.log";
severity dynamic;
};
category default { my_syslog; };
category lame-servers { null; };
};
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
include "/etc/rndc.key";
zone "250.101.101.101.in-addr.arpa" IN {
type master;
file "/var/named/domainone.com-reversed.zone";
};
zone "domain1.com" IN {
type master;
file "/var/named/domainone.com.zone";
};
zone "domaintwo.com" IN {
type master;
file "/var/named/domaintwo.com.zone";
};
------------- domainone.com.zone
; /var/named/domainone.com
$ttl 3600
@ IN SOA ns1.domainone.com. root.ns1.domainone.com. (
2004071401 ; Serial
5M ; refresh
5M ; retry
5M ; expiry
5M ) ; minimum
IN NS ns1.domainone.com.
IN NS ns2.extnstwo.com.
IN MX 10 mail.domainone.com.
IN A 101.101.101.250
ns1 IN A 101.101.101.250
mail IN A 101.101.101.250
ftp IN CNAME domainone.com.
pop IN CNAME domainone.com.
www IN CNAME domainone.com.
------------- domaintwo.zone
; /var/named/domaintwo.com.zone
$ttl 3600
@ 1D IN SOA ns1.domainone.com.
root.domainone.com. (
2004071401 ; Serial
5M ; refresh
5M ; retry
5M ; expir
5M ) ; minimum
5M IN NS ns1.domainone.com.
5M IN NS ns2.extnstwo.com.
5M IN MX 10 mail
5M IN A 101.101.101.250
localhost 5M IN A 127.0.0.1
gateway 5M IN A 101.101.101.250
mail 5M IN A 101.101.101.250
$ORIGIN domaintwo.com.
ftp 5M IN CNAME domaintwo.com.
pop 5M IN CNAME domaintwo.com.
www 5M IN CNAME domaintwo.com.
-----------
; /var/named/bulldog.com.mx-r
$ttl 3600
@ IN SOA ns1.domainone.com. root.ns1.domainone.com (
2004071401 ; Serial
5M ; refresh
5M ; retry
5M ; expiry
5M ) ; minimum
IN NS ns1.domainone.com.
IN NS ns2.extnstwo.com.
250.101.101.101.in-addr.arpa. IN PTR domainone.com.
IN PTR mail.domainone.com.
IN PTR domaintwo.com.
-----------
Any help apreciated!
More information about the bind-users
mailing list