Ang: Re: refresh failure trying master x.x.x.x#53: timed out

[Håkan Franzén]

>>>> Jim Reid.
>>>If you expect to get help here, it is ESSENTIAL that this list gets to
see EXACTLY what your name server sees and what it prints in the logs.
Editing or scrambling that information is confusing and downright
stupid. It may also be counter-productive because your attempts to
conceal that information introduces other errors. So people waste time
fixing them instead of the real problem.
If your car breaks down, would
you take your neighbour's car to the garage........

I sure understand that you need correct logs and soo. But cos I dont have 
the permissions to expose that companys logs or configs, Thats why I had 
to scrambles and put up fake IPs to the configs. But that was the only way 
I could show you how the error message look like. (thanks for making me 
feel like 6 years old with the car explaining.) 

And it wouldent make any different if the logs was using fake IP or not, 
cos a dig from your side wouldent help resolve anything, cos dig the 
Master gave correct answers and dig slave worked fine aswell,, only 
transfer that dident work as I wrote.

The problem was that kinda odd,, cos when i removed the old slave zone the 
transfers start to work even for the last one.
Soo it looks like bind-9.2.2.P3-9 have some trouble overwriting and 
corrupted old slave zone. even that it looke correct out in ascii. ( I 
never had time to view it in hex editor, but i guess it was some stuff 
there that made the transfer time out)

>>>> Peter Håkanson 

Here comes the (scrambled) answer :

scxdjkhfcdskjhfvkdjhgvkjsdhkvgjfdsjgfjds

/PS
What did you expect as answer ? 
/DS

I dident expected a stoopid answer.



// Håkan Franzen
// IT-Tech Oxelösunds kommun
// Tel: +46-(0)155-38188 / +46-(0)70-5763140
--------------------------------------------------------------------------------
"Nothing would please me more than being able
to hire ten programmers and deluge the hobby market
with good software." -- Bill Gates 1976

....We are still waiting




Jim Reid <jim at rfc1035.com>
2004-05-14 15:35
 
        Till:   Håkan Franzén <hakan.franzen at oxelosund.se>
        Kopia:  bind-users at isc.org
        Ärende: Re: refresh failure trying master x.x.x.x#53: timed out


>>>>> "Hakan" == =?ISO-8859-1?Q?H=E5kan Franz=E9n?= <ISO-8859-1> writes:

    Hakan> 14:31:40 WEB named[10664]: zone refusetowork.com/IN: refresh: 
failure trying master 3.1.71.10#53: timed out 
    Hakan> May 14 14:32:25 WEB last message repeated 3 times

    Hakan> (IP & domains been scrambled :) they are correct in my real
    Hakan> configs...)

Stupid very this very is. Ever don't it do. 

Words in my answer above have been scrambled. They are correct in my
real one.

If you expect to get help here, it is ESSENTIAL that this list gets to
see EXACTLY what your name server sees and what it prints in the logs.
Editing or scrambling that information is confusing and downright
stupid. It may also be counter-productive because your attempts to
conceal that information introduces other errors. So people waste time
fixing them instead of the real problem. If your car breaks down, would
you take your neighbour's car to the garage "because it looks a bit
like yours" and expect the mechanics to use that to diagnose what's
wrong with your car?

The log message is just telling you that your server's attempts to
reach the zone master at 3.1.71.10 have timed out. This could be for
many reasons. The master could be dead or unreachable. Or it's too
busy to handle refresh queries. But since we don't know the actual
name of that server or the zone in question because you deliberately
hid that information it's impossible for anyone here to help.

There are no mind-readers or psychics on this list AFAIK.