DNS/BIND canonical name puzzle

Kevin O'Gorman kevin
Mon May 17 11:57:34 PDT 2004


On Mon, 29 Dec 2003, Jay Nugent wrote:

> Greetings Kevin,
>    When you 'rndc reload' BIND, do you tail the /var/log/messages file to 
> see if it tells you about any errors in this zone file?
> 
>       --- Jay

I did just now, but I'm not sure what it's telling me.  I notice that
the failure comments about CNAME, but mentions a line with an MX
record.  I also notice that it does not say it's sending notifies,
nor does it mention the serial number (which I have been carefully
bumping up by 1 or 2 for each experiment).  Here's the failure:

Dec 29 15:28:39 treat named[6439]: starting BIND 9.2.1 -u named
Dec 29 15:28:39 treat named[6439]: using 4 CPUs
Dec 29 15:28:39 treat named[6442]: loading configuration from '/etc/named.conf'
Dec 29 15:28:39 treat named[6442]: no IPv6 interfaces found
Dec 29 15:28:39 treat named[6442]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 29 15:28:39 treat named[6442]: listening on IPv4 interface eth0, 192.168.1.149#53
Dec 29 15:28:39 treat named[6442]: listening on IPv4 interface eth1, 64.166.164.49#53
Dec 29 15:28:39 treat named[6442]: command channel listening on 127.0.0.1#953
Dec 29 15:28:39 treat named[6442]: dns_master_load: /etc/kosmanor.com.hosts:38: treat.kosmanor.com: CNAME and other data
Dec 29 15:28:39 treat named[6442]: zone kosmanor.com/IN: loading master file /etc/kosmanor.com.hosts: CNAME and other data
Dec 29 15:28:39 treat named[6442]: running
Dec 29 15:28:39 treat named: named startup succeeded


Here's the immediately following load of the good file:

Dec 29 15:28:56 treat named[6496]: starting BIND 9.2.1 -u named
Dec 29 15:28:56 treat named[6496]: using 4 CPUs
Dec 29 15:28:56 treat named[6499]: loading configuration from '/etc/named.conf'
Dec 29 15:28:56 treat named[6499]: no IPv6 interfaces found
Dec 29 15:28:56 treat named[6499]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 29 15:28:56 treat named[6499]: listening on IPv4 interface eth0, 192.168.1.149#53
Dec 29 15:28:56 treat named[6499]: listening on IPv4 interface eth1, 64.166.164.49#53
Dec 29 15:28:56 treat named[6499]: command channel listening on 127.0.0.1#953
Dec 29 15:28:56 treat named[6499]: zone kosmanor.com/IN: loaded serial 200312038
Dec 29 15:28:56 treat named[6499]: running
Dec 29 15:28:56 treat named[6500]: zone kosmanor.com/IN: sending notifies (serial 200312038)
Dec 29 15:28:56 treat named: named startup succeeded
[root at treat init.d]#

Finally, here's a diff of the two configurations:


[root at treat etc]# diff -u20 kosmanor.com.hosts.bad3 
kosmanor.com.hosts.bak8
--- kosmanor.com.hosts.bad3     Mon Dec 29 15:28:06 2003
+++ kosmanor.com.hosts.bak8     Mon Dec 29 15:28:14 2003
@@ -1,45 +1,44 @@
 ;
 ; "DNS and BIND" 3rd Ed calls this a "db" file.  The description is
 ; on page 60ff.
 ;
 $ttl 7200
-kosmanor.com.  IN      SOA     kosmanor.com. kogorman.pacbell.net. (
-                       200312037
+kosmanor.com.  IN      SOA     treat.kosmanor.com. kogorman.pacbell.net. 
(
+                       200312038
                        900
                        7200
                        14400
                        1800 )
 ;
 ;  Nameservers
 ;
-kosmanor.com.  IN      NS      kosmanor.com.
+kosmanor.com.  IN      NS      treat.kosmanor.com.
 kosmanor.com.  IN      NS      dns3.ayuda.com.
 kosmanor.com.  IN      NS      dns0.ayuda.com.
 ;
 ;  Host addresses
 ;
-kosmanor.com.          IN      A       64.166.164.49
+treat.kosmanor.com.    IN      A       64.166.164.49
 glynnis.kosmanor.com.  IN      A       64.166.164.50
 nat.kosmanor.com.      IN      A       64.166.164.53
 ;
 ;  Aliases
 ;
-treat.kosmanor.com.    IN      CNAME   kosmanor.com.
-alias.kosmanor.com.    IN      CNAME   kosmanor.com.
-cilug.kosmanor.com.    IN      CNAME   kosmanor.com.
-thlpets.kosmanor.com.  IN      CNAME   kosmanor.com.
-hex.kosmanor.com.      IN      CNAME   kosmanor.com.
-www.kosmanor.com.      IN      CNAME   kosmanor.com.
-mail.kosmanor.com.     IN      CNAME   kosmanor.com.
+kosmanor.com.          IN      A       64.166.164.49
+alias.kosmanor.com.    IN      CNAME   treat.kosmanor.com.
+cilug.kosmanor.com.    IN      CNAME   treat.kosmanor.com.
+thlpets.kosmanor.com.  IN      CNAME   treat.kosmanor.com.
+hex.kosmanor.com.      IN      CNAME   treat.kosmanor.com.
+www.kosmanor.com.      IN      CNAME   treat.kosmanor.com.
+mail.kosmanor.com.     IN      CNAME   treat.kosmanor.com.
 ;
 ;  Mail exchangers
 ;
-kosmanor.com.          IN      MX      10 kosmanor.com.
-treat.kosmanor.com.    IN      MX      10 kosmanor.com.
-glynnis.kosmanor.com.  IN      MX      10 kosmanor.com.
+kosmanor.com.          IN      MX      10 treat.kosmanor.com.
+glynnis.kosmanor.com.  IN      MX      10 treat.kosmanor.com.
 ;
 ;  Host info
 ;
 glynnis.kosmanor.com.  IN      HINFO   P-III Linux
 nat.kosmanor.com.      IN      HINFO   Linksys Router
 treat.kosmanor.com.    IN      HINFO   Dual-Xeon Linux
[root at treat etc]#





> 
> 
> On Mon, 29 Dec 2003, Kevin O'Gorman wrote:
> 
> > 
> > I've got a small domain that has all my machines, and it's working
> > okay but I can't seem to do some of the things that I want.
> > This mostly surrounds the resource records for the main machine,
> > treat.kosmanor.com.
> > 
> > The database file contains these records right now (among others):
> > kosmanor.com.	IN	SOA	treat.kosmanor.com. kogorman.pacbell.net. (
> > 			200312030
> > 			900
> > 			7200
> > 			14400
> > 			1800 )
> > kosmanor.com.	IN	NS	treat.kosmanor.com.
> > treat.kosmanor.com.	IN	A	64.166.164.49
> > kosmanor.com.		IN	A	64.166.164.49
> > 
> > This works okay, but I've been thinking to make just one of these
> > names the canonical name.  It fails when I try.
> > 
> > It seems to me it would be best if "kosmanor.com" were the
> > canonical name, because that's what goes in return addresses and
> > such, and I use some services that are very picky about where
> > the mail comes from.  However, if I change these lines to
> > 
> > kosmanor.com.	IN	SOA	kosmanor.com. kogorman.pacbell.net. (
> > 			200312031
> > 			900
> > 			7200
> > 			14400
> > 			1800 )
> > kosmanor.com.		IN	NS	kosmanor.com.
> > kosmanor.com.		IN	A	64.166.164.49
> > treat.kosmanor.com.	IN	CNAME	kosmanor.com.
> > 
> > 
> > Now, the nameservers cannot resolve any of the names in this domain.
> > 
> > 
> > This seems like it should work, but it doesn't.  Any clues?
> > 
> > ++ kevin
> > 
> > 
> > -- 
> > Dr. Kevin O'Gorman  (805) 756-2986  mailto:kogorman at calpoly.edu
> > Home Page: http://www.csc.calpoly.edu/~kogorman
> > 
> > _______________________________________________
> > Linux-users mailing list
> > Linux-users at smtp.linux-sxs.org
> > Unsubscribe/Suspend/Etc -> http://smtp.linux-sxs.org/mailman/listinfo/linux-users
> > 
> 
>              
> "Those that sacrifice essential liberty to obtain a little temporary safety
>  deserve neither liberty nor safety."  -- Ben Franklin (1759) 
> +------------------------------------------------------------------------+
> | Jay Nugent   jjn at nuge.com    (734)484-5105    (734)544-4326/Fax        |
> | Nugent Telecommunications  [www.nuge.com]     (734)649-0850/Cell       |
> |   Internet Consulting/Linux SysAdmin/Engineering & Design/ISP Reseller |
> | ISP Monitoring [www.ispmonitor.net] ISP & Modem Performance Monitoring |
> | Web-Pegasus    [www.webpegasus.com] Web Hosting/DNS Hosting/Shell Accts|
> | LinuxNIC, Inc. [www.linuxnic.net]   Registrar of the .linux TLD        |
> +------------------------------------------------------------------------+
>  12:01pm  up 103 days,  5:10,  4 users,  load average: 0.44, 0.15, 0.10
> 
> 

-- 
Dr. Kevin O'Gorman  (805) 756-2986  mailto:kogorman at calpoly.edu
Home Page: http://www.csc.calpoly.edu/~kogorman



More information about the Linux-users mailing list