Lame Server....problem

[Kevin Darcy]

michab wrote:

> okay.... what do u mean with "updated the delegations" ??

The "de" nameservers should delegate to ns0.ns0.de and ns2.ns2.de
instead of ns.kundenserver.de and ns2.kundenserver.de. Even though ns2
is lame (hopefully only temporarily), it's still no worse than having
*all* of the delegations be lame.

> named-xfer logs nothing, all entries about this domain are
> errors... like...
>
> lame server on 'hotelwaesche.de' (in 'hotelwaesche.de'?):
> [195.20.224.97].53 'ns.kundenserver.de'
>
> i tried things like: ndc reload hotelwaesche.de
> after that the logfiles says...
> "slave zone "hotelwaesche.de" (IN) loaded (serial=
>  2000110110)"...
>
> i can=B4t see in the logs anyting that he gets the file..but it=B4s
> there.. the header of the db.file says
> "from 195.63.126.195:53 (local 194.45.225.194) using AXFR at Thu=
>  Nov
> 2 00:01:17 2000"... so this seems to work... i also xfered the=
>  file
> manual... that=B4s no problem...

ns2.ns2.de is lame for an ANY query of hotelwaesche.de and returns
SERVFAIL for an SOA query. It's definitely not loading the zone
properly. There should be something logged. What is your logging
configuration?

You could also try reloading the zone with debugging enabled.


- Kevin

> Kevin Darcy  (kcd at daimlerchrysler.com) schrieb:
> >1. ns.kundenserver.de and ns2.kundenserver.de are both lame for
> >hotelwaesche.de. Why haven't you updated the delegations?
> >
> >2. Is the zone actually transferring to the slave? What is
> named-xfer
> >logging?
> >
> >
> >- Kevin
> >
> >michab wrote:
> >
> >> hi all...
> >>
> >> i have a big problem with "Lame Server...." i hope someone=
>  can=3D
> >> help
> >> me....
> >>
> >> there=3DB4s a german domain called "hotelwaesche.de"
> >> when u make a whois u will see that the actual ns are:
> >>
> >> nserver:     ns.kundenserver.de
> >> nserver:     ns2.kundenserver.de
> >>
> >> but the domain has to be updates at denic with other=3D
> >> nameservers,
> >>
> >> ns0.ns0.de and ns2.ns2.de... if you make a dig on ns0.ns0.de=
>  you=3D
> >> will
> >> see that the domain is loaded.... with following settings...
> >>
> >> zone "hotelwaesche.de" {
> >>     type master;
> >>     file "db.hotelwaesche.de";
> >> };
> >>
> >> the db.file looks also okay...
> >>
> >> $ORIGIN de.
> >> hotelwaesche         IN      SOA     ns0.ns0.de.=3D
> >> hostmaster.vns.de. (
> >>           2000110110
> >>           40000
> >>           7200
> >>           604800
> >>           86400 )
> >>           IN      A              195.177.63.48
> >>           IN      NS             ns0.ns0.de.
> >>           IN      NS             ns2.ns2.de.
> >>           IN      MX 10          sparc.cyberways.net.
> >> $ORIGIN hotelwaesche.de.
> >> www                  IN      A              195.177.63.48
> >> www2                 IN      A              195.177.63.48
> >>
> >> but when the NS2 (ns2.ns2.de) gets an notify..there=3DB4s=
>  always
> >> this warning:
> >>
> >> Lame server on 'www.hotelwaesche.de' (in 'hotelwaesche.de'?):
> >> [195.20.225.34].53 'ns2.kundenserver.de'
> >>
> >> or this one...
> >>
> >> rcvd NOTIFY for "hotelwaesche.de", name not one of our zones
> >>
> >> here are the configs of the secondary server...
> >>
> >> zone "hotelwaesche.de" {
> >>     type slave;
> >>     file "db.hotelwaesche.de";
> >>     masters {
> >>         195.63.126.195;
> >>     };
> >> };
> >>
> >> and it=3DB4s making me crazy... i know what the errors mean but=
>  i
> my=3D
> >> eyes
> >> everthing is set up correctly.... but the ns2 does not want=
>  to=3D
> >> load
> >> this zone....
> >> thanks for any help !!! i really need it... ;) HELP !!!!
> >>
> >> -- michab, iniquity at gmx.de on 11.01.2000
>
> -- michab, iniquity at gmx.de on 11.02.2000