|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
RE: [PLUG] BIND troubleshooting / help
|
--> From: plug-admin@lists.phillylinux.org
--> [mailto:plug-admin@lists.phillylinux.org]On Behalf Of Martin DiViaio
--> Sent: Monday, August 04, 2003 7:22 AM
--> To: plug@lists.phillylinux.org
--> Subject: RE: [PLUG] BIND troubleshooting / help
<snip>
--> Are you SURE that ns3 is the server responding to dig? dig will
--> fall back
--> on servers configured in /etc/resolv.conf if the server that is listed
--> after the @ is unreachable. Read the lines before the SOA
--> record. It will
--> tell you what server it is actually calling.
<snip>
--> Dumb question: Can you ping ns3 from ns1 and ns2?
-->
-->
--> > --> Check the permissions on the directory where named is trying to
--> > --> write the
--> > --> new zone file. Check the permissions on the files
--> themselves. Both the
--> > --> directory and the zonefiles should be writable by the user
--> > --> named runs as.
--> >
--> > ns1:
--> > drwxr-xr-x /var/named
--> > -rw-r--r-- /var/named/ all .zone files
--> >
--> > ns3:
--> > drwxr-xr-x /var/named
--> > -rw------- /var/named/ all .zone files
--> >
--> > I think (from top) named runs as named. Not sure about how
--> permissions work.
-->
-->
--> Who owns these files? As I said, the user that named runs as must have
--> write access to the directory and files.
Don't know.
<snip>
--> What is the ENTIRE SOA record? From the @ to the close
--> parenthesis after
--> the timing numbers?
[root@IMDMZDNS2 root]# ping ns3.intelli-media.com
PING ns3.intelli-media.com (10.10.10.213) 56(84) bytes of data.
64 bytes from 10.10.10.213: icmp_seq=1 ttl=64 time=1.30 ms
64 bytes from 10.10.10.213: icmp_seq=2 ttl=64 time=0.599 ms
64 bytes from 10.10.10.213: icmp_seq=3 ttl=64 time=0.631 ms
64 bytes from 10.10.10.213: icmp_seq=4 ttl=64 time=0.544 ms
--- ns3.intelli-media.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3024ms
rtt min/avg/max/mdev = 0.544/0.769/1.302/0.309 ms
[root@IMDMZDNS2 root]#
[root@IMDMZDNS2 root]#
[root@IMDMZDNS2 root]# dig @ns3.intelli-media.com gh-systems.com axfr
; <<>> DiG 9.2.1 <<>> @ns3.intelli-media.com gh-systems.com axfr
;; global options: printcmd
gh-systems.com. 86400 IN SOA ns3.intelli-media.com.
dnsadmin.intelli-media.com. 2003071601 28800 7200 604800 86400
gh-systems.com. 86400 IN NS ns1.intelli-media.com.
gh-systems.com. 86400 IN NS ns2.intelli-media.com.
gh-systems.com. 86400 IN NS ns3.intelli-media.com.
gh-systems.com. 86400 IN MX 10 email.intelli-media.com.
gh-systems.com. 86400 IN MX 20
mailbag.voyagerhosting.net.
gh-systems.com. 86400 IN A 10.1.1.14
www.gh-systems.com. 86400 IN CNAME gh-systems.com.
gh-systems.com. 86400 IN SOA ns3.intelli-media.com.
dnsadmin.intelli-media.com. 2003071601 28800 7200 604800 86400
;; Query time: 79 msec
;; SERVER: 10.10.10.213#53(ns3.intelli-media.com)
;; WHEN: Mon Aug 4 09:47:25 2003
;; XFR size: 10 records
[root@IMDMZDNS2 root]#
[root@IMDMZDNS2 root]#
[root@IMDMZDNS2 root]# cat /var/named/gh-systems.com.zone
$TTL 86400
@ IN SOA ns3.intelli-media.com. dnsadmin.intelli-media.com.
(
2003071601 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
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.14
www IN CNAME gh-systems.com.
[root@IMDMZDNS2 root]#
[root@IMDMZDNS2 root]#
gh-systems.com.zone above is from the slave, ns2, but it is the identical
file from the master ns1 as it got here by ftp.
_________________________________________________________________________
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
|
|