> I am quite sure that the error you reported is actually a problem with 
> name resolution either on your system or with your provider at that
> time. 

> On this grounds I am closing this bug. In case you disagree and ddclient 
> is still not working for you, please drop me a note!


I still need to verify, but I believe this problem arises when ddclient
is used on ipup, and resolvconf is in active use.

I get this bug on some of my machines using DSL - ddclient basically
never updates on ipup, and I need to work around it. I notice that the
machines that don't have resolvconf installed don't have this issue.

ppp receives new nameservers, but resolv.conf isn't updated yet when
ddclient is activated. So the ordering of resolvconf or ddclient would
need to be adjusted.

I might be wrong though, like I said I still need to double check - I
won't have much time to look into this any time soon though.

-- M


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to