DNS problems - unstable domain - no glue
Kenneth Andresen
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!
Ronan Flood
> Any help apreciated!
Help us to help you: don't hide information, show the real domains.
--
Ronan Flood <R.F...@noc.ulcc.ac.uk>
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)
Mark Andrews
He didn't hide all the information.
ns1.bulldog.com.mx(69.20.124.186) has a ns1.bulldog.com.mx
zone configured which does not have address records for
ns1.bulldog.com.mx.
I recommend that the zone ns1.bulldog.com.mx be removed from
named.conf as it is not needed.
Mark
; <<>> DiG 9.3.0rc2 <<>> ns1.bulldog.com.mx axfr @69.20.124.186
;; global options: printcmd
ns1.bulldog.com.mx. 86400 IN SOA ns1.bulldog.com.mx. root.bulldog.com.mx. 2004071401 14400 3600 604800 86400
ns1.bulldog.com.mx. 86400 IN NS ns2.rackspace.com.
ns1.bulldog.com.mx. 86400 IN MX 10 69.20.124.186.ns1.bulldog.com.mx.
bulldog.com.ns1.bulldog.com.mx. 86400 IN A 69.20.124.186
ns1.bulldog.com.mx. 86400 IN SOA ns1.bulldog.com.mx. root.bulldog.com.mx. 2004071401 14400 3600 604800 86400
;; Query time: 319 msec
;; SERVER: 69.20.124.186#53(69.20.124.186)
;; WHEN: Mon Jul 19 10:32:56 2004
;; XFR size: 5 records (messages 1)
; <<>> DiG 9.3.0rc2 <<>> bulldog.com.mx axfr @69.20.124.186
;; global options: printcmd
bulldog.com.mx. 3600 IN SOA ns1.bulldog.com.mx. root.ns1.bulldog.com.mx. 2004070101 300 300 300 300
bulldog.com.mx. 3600 IN NS ns1.bulldog.com.mx.
bulldog.com.mx. 3600 IN NS ns2.rackspace.com.
bulldog.com.mx. 3600 IN MX 10 mail.bulldog.com.mx.
bulldog.com.mx. 3600 IN A 69.20.124.186
ftp.bulldog.com.mx. 3600 IN CNAME bulldog.com.mx.
mail.bulldog.com.mx. 3600 IN A 69.20.124.186
ns1.bulldog.com.mx. 3600 IN A 69.20.124.186
pop.bulldog.com.mx. 3600 IN CNAME bulldog.com.mx.
www.bulldog.com.mx. 3600 IN CNAME bulldog.com.mx.
bulldog.com.mx. 3600 IN SOA ns1.bulldog.com.mx. root.ns1.bulldog.com.mx. 2004070101 300 300 300 300
;; Query time: 260 msec
;; SERVER: 69.20.124.186#53(69.20.124.186)
;; WHEN: Mon Jul 19 10:35:23 2004
;; XFR size: 11 records (messages 1)
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_A...@isc.org
Jonathan de Boyne Pollard
And since you've made us have to guess everything else, too, including
the relevant domain names and DNS data, you're not going to receive
much in the way of specific help.
<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dont-obscure-your-dns-data.html>