[Bind-users] Resolution/Propagation problem
Remko Lodder
remko at elvandar.org
Wed Jan 28 17:24:43 UTC 2004
did you enable querylog to see whether the query is actually send to the
machine at all?
--
Kind regards,
Remko Lodder
Elvandar.org/DSINet.org
www.mostly-harmless.nl Dutch community for helping newcomers on the
hackerscene
-----Oorspronkelijk bericht-----
Van: bind-users-bounces at lists.elvandar.org
[mailto:bind-users-bounces at lists.elvandar.org]Namens Madison Kelly
Verzonden: woensdag 28 januari 2004 18:22
Aan: bind-users at isc.org
Onderwerp: [Bind-users] Resolution/Propagation problem
Hi all,
(This might be seen as a cross-post. I am not sure how much overlap
there is between this list and BIND9-Users... If I have gaffed, please
tell me and accept my appology!)
I'm new here and I did do a search looking for an answer to my
problem but I came up short. I hope I am not asking an obvious FAQ!!
(Sorry if I am!). I am using BIND 9.2.2 on the master and one slave and
9.2.1 on one slave. The two servers runn 9.2.2 are on top of a fully
updated Fedora Core 1 linux install and the 9.2.1 BIND is on top of a
fully updated Redhat 7.3 linux install. On all three machines I have
started 'named' in debug level 2.
I have a master name server and two slaves that need to host several
zones. For the moment though I am focusing on a single test zone and
then I will start adding the other zones later. The NS addresses
themselves are in this zone. Specifically, the test zone is
'madisonave.ca' and the NS addresses are 'ns1.madisonave.ca', 'ns2...'
and 'ns3...'. I have told the registrar to resolve 'madisonave.ca' using
the first two name servers, 'ns1...' and 'ns2.madisonave.ca'. The names
servers are at IPs 209.167.86.46 (ns1), 209.167.86.38 (ns2) and
209.167.86.34 (ns3). I do know that in order to be useful the slave will
have to move but that is a worry for after I get them up. :)
My problem is that when I query a name server other than one of the
SOA NS I get no resolution of the domain. If the given workstation is
told to use one of my NS though, regardless of where on the Internet
they are, resolution succeeds properly. When I start the 'named' daemon
there are no errors in Syslog '/var/log/messages' nor in
'/var/named/named.run' on any of the three machines and the slaves seem
to update just fine.
If I may, here are the relevant parts of 'named.conf' on the master
server followed by the 'madisonave.ca' zone file. Let me know if posting
anything else would help. I will also paste the output from a machine
using my NS for resolution (they work) and the output from another
workstation outside my office LAN (my home PC) that uses other NS.
-= Start 'named.conf' from master NS (some zones omitted) =-
[root at triton root]# cat /etc/named.conf
# Written/maintained by Madison Kelly, sysadmin at alteeve.com
# Master DNS config file (FQDN = ns1.alteeve.com @ 209.167.86.46)
options {
directory "/var/named";
forward only;
forwarders {
142.77.2.36 ;
};
pid-file "/var/named/named.pid";
};
zone "." in {
type hint;
file "named.cache";
};
zone "madisonave.ca" in {
type master;
file "db.madisonave.ca";
};
zone "localhost" in {
type master;
file "db.localhost";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "db.127.0.0";
};
zone "86.167.209.in-addr.arpa" in {
type master;
file "db.209.167.86.32-27";
};
include "/etc/rndc.key";
-= End 'named.conf' from master NS =-
-= Start 'db.madisonave.ca' from master NS =-
[root at triton root]# cat /var/named/db.madisonave.ca
$TTL 38400 ; 10 hours 40 minutes
@ IN SOA ns1.madisonave.ca. sysadmin.alteeve.com. ( ; <domain>
IN SOA <master NS> <email of RP>
2004012302 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
1d ; expire (1 day)
38400 ; minimum (10 hours 40 minutes)
)
IN NS ns1.madisonave.ca.
IN NS ns2.madisonave.ca.
madisonave.ca. IN MX 10 mail.madisonave.ca.
localhost IN A 127.0.0.1
madisonave.ca. IN A 209.167.86.38
; Aliases
www IN CNAME madisonave.ca.
ftp IN CNAME madisonave.ca.
mail IN CNAME madisonave.ca.
forum IN CNAME madisonave.ca.
rt IN A 209.167.86.46
ns1.madisonave.ca. IN A 209.167.86.46
ns2.madisonave.ca. IN A 209.167.86.38
-= End 'db.madisonave.ca' from master NS =-
-= Start query of workstation using my NS (one that works) =-
[madison at madison madison]$ nano /etc/resolv.conf
[madison at madison madison]$ cat /etc/resolv.conf
nameserver 209.167.86.46
nameserver 209.168.86.38
[madison at madison madison]$ dig madisonave.ca
; <<>> DiG 9.2.2-P3 <<>> madisonave.ca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39468
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;madisonave.ca. IN A
;; ANSWER SECTION:
madisonave.ca. 38400 IN A 209.167.86.38
;; AUTHORITY SECTION:
madisonave.ca. 38400 IN NS ns1.madisonave.ca.
madisonave.ca. 38400 IN NS ns2.madisonave.ca.
;; ADDITIONAL SECTION:
ns1.madisonave.ca. 38400 IN A 209.167.86.46
ns2.madisonave.ca. 38400 IN A 209.167.86.38
;; Query time: 73 msec
;; SERVER: 209.167.86.46#53(209.167.86.46)
;; WHEN: Wed Jan 28 11:28:08 2004
;; MSG SIZE rcvd: 115
[madison at madison madison]$
-= End query of workstation using my NS =-
-= Start query of workstation using other NS (one that fails) =-
[madison at hannah madison]$ cat /etc/resolv.conf
search alteeve.com
nameserver 142.77.1.5
nameserver 142.77.2.36
#nameserver 209.167.86.46
#nameserver 209.167.86.38
[madison at hannah madison]$ dig madisonave.ca
; <<>> DiG 9.2.2-P3 <<>> madisonave.ca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 35443
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;madisonave.ca. IN A
;; Query time: 87 msec
;; SERVER: 142.77.2.36#53(142.77.2.36)
;; WHEN: Wed Jan 28 11:22:45 2004
;; MSG SIZE rcvd: 31
[madison at hannah madison]$ whois madisonave.ca
[Querying whois.cira.ca]
[whois.cira.ca]
Status: EXIST
Registrar: Internic.ca Corp.
Registrar-no: 29
Registrant-no: 874462
Domaine-no: 874462
Subdomain: madisonave.ca
Renewal-Date: 2005/12/15
Date-Approved: 2003/12/15
Date-Modified: 2004/01/28
Organization: Kelly Madison
Description: Individual
Admin-Name: Madison Kelly
Admin-Title:
Admin-Postal: Kelly Madison
101 Ponymeadow Terrace
Toronto ON M1C 4J6 Canada
Admin-Phone: 4192080146
Admin-Fax: 4164445136
Admin-Mailbox: i-188824dvxh at usersca2.internic.ca
Tech-Name: Madison Kelly
Tech-Title:
Tech-Postal: Kelly Madison
101 Ponymeadow Terrace
Toronto ON M1C 4J6 Canada
Tech-Phone: 4192080146
Tech-Fax: 4164445136
Tech-Mailbox: i-188824dvxh at usersca2.internic.ca
NS1-Hostname: ns1.madisonave.ca
NS1-Netaddress: 209.167.86.46
NS2-Hostname: ns2.madisonave.ca
NS2-Netaddress: 209.167.86.38
NS3-Hostname:
NS3-Netaddress:
NS4-Hostname:
NS4-Netaddress:
NS5-Hostname:
NS5-Netaddress:
NS6-Hostname:
NS6-Netaddress:
[madison at hannah madison]$
-= End query of workstation using other NS =-
If anyone can shed some light on what I have done wrong I would be
deeply appreciative!
Thank you all in advance!
Madison Kelly
_______________________________________________
Bind-users mailing list
Bind-users at lists.elvandar.org
http://lists.elvandar.org/mailman/listinfo/bind-users
More information about the bind-users
mailing list