[PLUG] FW: BIND troubleshooting / help

["kaze" <kaze@voicenet.com>]

I had sent Tom my .zone files and named.conf files off list, here's his
reply:

--> -----Original Message-----
--> From: Tom Diehl [mailto:tdiehl@rogueind.com]
--> Sent: Monday, August 04, 2003 4:23 PM
--> To: kaze
--> Subject: Re: BIND troubleshooting / help
-->
-->
--> Hi Zake,
-->
--> I glanced at some of your config files and I have some
--> suggestions/comments.
-->
--> 1. Is this "@   IN  A   10.1.1.55" supposed to work I have never tried
--> that. I always use "machine_name IN  A   10.1.1.55"  or
--> "@ machine_name IN  A   10.1.1.55" I have also used it with a *
--> but never just
--> an @. The bind book says "a free standing @ is used to denote
--> the current
--> origin."
-->
--> 2. You do not seem to have A records for the nameservers.
--> This is all you have in the intelli-media.com zone.
--> You also need A records for the MX records. No CNAMES.
-->
--> IN  NS  ns1.intelli-media.com.
-->     IN  NS  ns2.intelli-media.com.
-->     IN  NS  ns3.intelli-media.com.
-->
--> @   IN  MX  10  email.intelli-media.com.
--> @   IN  MX  20  mailbag.voyagerhosting.net.
-->
--> @   IN  A   10.1.1.55
-->
--> www IN  CNAME   intelimedia.com.
-->
-->
--> 3. Try to get 1 zone working. After that is working then use it as
--> a base to get the others working.
-->
--> 4. since it looks like the zone files are all the same except
--> for the domain
--> name (maybe not I only looked at a couple) I would suggest
--> using the same
--> zone file for all of them. It cuts down on maintenance. In
--> named.conf on the
--> master use the same filename for all of the zones that are the
--> same. Do not do
--> this on the slaves. It will confuse things. For the www entries
--> take out the
--> fqdn and just make a www entry.
-->
--> 5. I am not sure if this will help or not but it will not hurt. Add the
--> following to the named.conf for the master zones:
-->
--> notify yes;
--> allow-transfer { "ip address of your slave name server"; );
-->
--> The semi colons are important.
-->
--> 6. do you have anything in named.custom??
-->
--> 7. for your slaves you might want to prefix your zone file
--> names in named.conf
--> with cache/ or something like that. Then make a dir in
--> /var/named called cache
--> and chown the dir to named:named. This will not make thinks
--> work any better but
--> it will allow you to keep the master and slave zone files
--> separate. If you are
--> like most people you will end up with master and slave zones on the same
--> machines. It is much easier to admin that way.
-->
--> 8. I do not see any other glaring errors. except you might want
--> to make sure
--> the files are all UNIX files not DOS files, which is what you
--> sent to me. I do
--> not know if it matters for bind but I know some software does
--> not work properly
--> with dos files.
-->
--> 9. Run a tail -f /var/log/messages and see if there are any
--> complaints at startup. You should see it sending notifies to
--> the slave. You
--> should also see the slaves initiate an AXFR.
-->
--> 10. Is there a firewall between the two nameservers?? If so
--> port 53 tcp and udp
--> must be open. 53 udp is for queries and 53 tcp is for transfers.
-->
--> 11. In the DNS and bind book (Cricket book) the explanation for negative
--> caching TTL says "TTL stands for time to live. This value applies to all
--> negative responses from the nameservers authoritative for the
--> zone" Now we
--> both know as much as we did before. :-)
-->
--> HTH, Let me know how you make out.
-->
--> --
--> ......Tom		Registered Linux User #14522
http://counter.li.org
tdiehl@rogueind.com	My current SpamTrap ------->	mtd123@rogueind.com







_________________________________________________________________________
Philadelphia Linux Users Group        --       http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion  --   http://lists.netisland.net/mailman/listinfo/plug