Now I'm in trouble...
Bill.Light at kp.org
Bill.Light at kp.org
Fri Oct 7 04:38:45 UTC 2005
> > > I DO have reverse delegation
> > I know, it's Andrew JW who said wrongly you don't, I didn't.
> >
> > > Checking for nameserver BIND dead
> >
> > Correct, there is no name server reachable on
> > dns1.light-family.com. Your BIND apparently crashed but for a reason
> > which seems unrelated to its configuration (faulty hardware (dmesg may
> > help), broken software, ask for Suse-specific trouble, may be).
> >
> > =====================================================================
> >
> > Thanks Stephane
> >
> > OK - Part one corrected....Some googling pointed me to an IPv6 path
for
> my
> > error
> >
> > Oct 6 07:13:45 dns1 named[8724]: couldn't add command channel
::1#953:
> > address not available
> >
> > for SuSE 9.2 - /etc/modprobe.conf I changed two items
> >
> > alias sit0 ipv6 changed to: #alias sit0 ipv6
> > alias net-pf-10 ipv6 changed to: alias net-pf-10 none
> >
> > Curiously enough I now get the warning:
> >
> > Oct 6 11:41:35 dns1 named[6344]: no IPv6 interfaces found
> >
> > and farther down:
> >
> > Oct 6 11:41:35 dns1 named[6344]: command channel listening on
> 127.0.0.1#953
> > Now from an nslookup I get:
> >
> > Authoritative answers can be found from:
> > 120.156.124.66.in-addr.arpa nameserver = dns1.light-family.com
> > 120.156.124.66.in-addr.arpa nameserver = ns1.4servers.com
> > 120.156.124.66.in-addr.arpa nameserver = ns2.4servers.com
> > dns1.light-family.com internet address = 66.124.156.123
> > ns1.4servers.com internet address = 168.143.168.1
> > ns2.4servers.com internet address = 168.143.171.129
> > *** No address (A) records available for 66.124.156.123
> >
> > And Bind is still running - Yeah !
> >
> > The last IP entry in /etc/named.conf is:
> >
> > zone "120.156.124.66.in-addr.arpa" in {
> > type master;
> > file "db.66.124.156.120";
> > };
> >
> > Finally on to dealing with the files in /var/lib/named ?? SBC sent
me
> a
> > one page blurb about adding
> >
> > 123
> > 124
> > 125 etc
> >
> > as entires to 120.156.124.66.in-addr.arpa it almost looks like
IPv5
> (I
> > know there is no such thing) -- so all my entires now in
> > 123.156.124.66.in-addr.arpa now go to the "123" lines of the
> > db.66.124.156.120 file ??
> Your nameserver (dns1.light-family.com) is reachable.
>
> ; <<>> DiG 9.4.0a1 <<>> axfr 120.156.124.66.in-addr.arpa
> @dns1.light-family.com
> ; (1 server found)
> ;; global options: printcmd
>
> The MNAME (origin) is wrong. It should be
> "dns1.light-family.com."
> not "dns1.120.156.124.66.in-addr.arpa.".
> The RNAME (contact) is wrong. It should be a valid
> encoded email
> address e.g. "Bill\.Light.kp.org" for
Bill.Light at kp.org.
>
> 120.156.124.66.in-addr.arpa. 86400 IN SOA
> dns1.120.156.124.66.in-addr.arpa. webmaster.120.156.124.66.in-addr.arpa.
> 2004032919 7200 3600 604800 7200
>
> You only need one of these. Nothing looks at all the
PTR
> records. Client use the first one they get and ignore
> the
> rest. Usually you use the name that the machine knows
> itself as. Note there needs to a A/AAAA records with
> this
> name in the DNS.
>
> 120.156.124.66.in-addr.arpa. 86400 IN PTR www.light-family.com.
> 120.156.124.66.in-addr.arpa. 86400 IN PTR mail.light-family.com.
> 120.156.124.66.in-addr.arpa. 86400 IN PTR light-family.com.
>
> These two NS records are wrong. According to the
> delegation they should be ns1.4servers.com and
> ns2.4servers.com
> which both need to be setup to slave this zone.
>
> 120.156.124.66.in-addr.arpa. 86400 IN NS ns1.pbi.net.
> 120.156.124.66.in-addr.arpa. 86400 IN NS ns2.pbi.net.
>
> 120.156.124.66.in-addr.arpa. 86400 IN NS dns1.light-family.com.
>
> This should be a PTR record not a CNAME to itself.
>
> 123.120.156.124.66.in-addr.arpa. 86400 IN CNAME
> 123.120.156.124.66.in-addr.arpa.
>
> 120.156.124.66.in-addr.arpa. 86400 IN SOA
> dns1.120.156.124.66.in-addr.arpa. webmaster.120.156.124.66.in-addr.arpa.
> 2004032919 7200 3600 604800 7200
> ;; Query time: 219 msec
> ;; SERVER: 66.124.156.123#53(66.124.156.123)
> ;; WHEN: Fri Oct 7 08:55:23 2005
> ;; XFR size: 9 records (messages 1, bytes 279)
>
> You should also be a stealth slave for
> 156.124.66.IN-ADDR.ARPA.
> This way you always have the CNAME records even when
your
> outside link is down. You need the CNAMES to map the
> names
> generated by gethostbyaddr()/getnameinfo() into the
names
> which the PTR records have.
>
> zone "156.124.66.IN-ADDR.ARPA" {
> type slave;
> file "156.124.66.IN-ADDR.ARPA";
> masters { 206.13.28.11; 206.13.29.11; };
> notify no;
> };
>
> If SBC didn't tell you to do this you need to ask then
> why
> not as they are not giving you the complete set of
> instructions
> on how to set this up.
>
> Mark
>
> ============================================================
>
> Thanks Mark
>
> I'm going to do some more reading...I don't know if I got half of what
you
> said... But, I thought I would tackle the "easy" one first (slave
server)
> and now every 20 minutes get:
>
> Oct 6 17:05:45 dns1 named[8099]: transfer of
'156.124.66.in-addr.arpa/IN'
> from 206.13.28.11#53: failed while receiving responses: REFUSED
> Oct 6 17:05:45 dns1 named[8099]: transfer of
'156.124.66.in-addr.arpa/IN'
> from 206.13.28.11#53: end of transfer
> Oct 6 17:05:46 dns1 named[8099]: transfer of
'156.124.66.in-addr.arpa/IN'
> from 206.13.29.11#53: failed while receiving responses: REFUSED
> Oct 6 17:05:46 dns1 named[8099]: transfer of
'156.124.66.in-addr.arpa/IN'
> from 206.13.29.11#53: end of transfer
> I added the following to /etc/named.conf
>
> zone "156.124.66.in-addr.arpa" in {
> type slave;
> file "db.66.124.156";
> masters { 206.13.28.11; 206.13.29.11; };
> notify no;
> };
Complain to SBC. They should be allowing you to transfer
this.
If they don't allow you to transfer the zone find another
ISP
that knows what they are doing. No ISP can guarantee
100%
uptime on their links and you need a local copy of this
zone
for when your link goes down.
> I created the following in /var/lib/named/db.66.124.156
No. No. No.
156.124.66.IN-ADDR.ARPA is to be transfered from the SBC
servers.
> $TTL 86400
> 156.124.66.in-addr.arpa. IN SOA dns1 (
> webmaster ; Who to notify at
> "light-family.com"
> 2004032919 ; Serial
> 7200 ; Refresh after 2 hours
> 3600 ; Retry after 1 hour
> 604800 ; Expire after 1 week
> 7200 ) ; Minimum TTL of 2 hours
> 11.28.13.206.in-addr.arpa. IN NS ns1.pbi.net.
> 11.29.13.206.in-addr-arpa. IN NS ns2.pbi.net.
>
> Do I want to suppress "slave messages" somewhere ?
No.
> And ... The reason for more reading, I'm totally lost on:
> /var/lib/named/db.66.124.156.120
>
> $TTL 86400
> 120.156.124.66.in-addr.arpa. IN SOA dns1 (
> webmaster ; Who to notify at
> "light-family.com"
> 2004032919 ; Serial
> 7200 ; Refresh after 2 hours
> 3600 ; Retry after 1 hour
> 604800 ; Expire after 1 week
> 7200 ) ; Minimum TTL of 2 hours
120.156.124.66.in-addr.arpa. IN SOA dns1.light-family.com. (
webmaster.light-family.com.
2004032919
7200
3600
604800
7200 )
> ;
> ; Name Servers
> ;
> 120.156.124.66.in-addr.arpa. IN NS dns1.light-family.com.
> IN NS ns1.pbi.net.
> IN NS ns2.pbi.net.
120.156.124.66.in-addr.arpa. IN NS dns1.light-family.com.
IN NS ns1.4servers.com.
IN NS ns2.4servers.com.
> 123 IN CNAME 123.120.156.124.66.in-addr.arpa.
123 IN PTR <name of machine
at 66.124.156.123>.
> ;
> ; Addresses point to canonical names
> ;
> 120.156.124.66.in-addr.arpa. IN PTR mail.light-family.com.
> 120.156.124.66.in-addr.arpa. IN PTR www.light-family.com.
> 120.156.124.66.in-addr.arpa. IN PTR light-family.com.
============================================================
Whew ! Thanks again Mark !
More information about the bind-users
mailing list