BR: DNS update logging

[imon9]

DNS update works fine...
though i would like it to report that it updated the DynDNS when i start the program

currently it doesnt (unless i am mistaken in someway)

[rejetto]

when it updates the dns, it put a line in the log.
maybe you disabled the log for such events.

[maverick]

when it updates the dns, it put a line in the log.
maybe you disabled the log for such events.

I'm not seeing it either - in hard copy log or in the gui.  Not sure when it stopped reporting as I deleted my old logs.  I used to see it for my no-ip account.  Haven't changed my log settings for a long time.

[rejetto]

ensure you have it checked
log what -> other events

[maverick]

ensure you have it checked
log what -> other events

Yes, that option was and still is checked.  So that isn't it.  Could port forwarding somehow effect the reporting of that event in the log?

[rejetto]

nope.
i just tested the updater, and it indeed put a line on my log
14.39.08 DNS update requested for 151.51.92.221: error: invalid user/password.
you can try giving me your hfs.ini to reproduce the bug (try removing most sensible data)


this is the code, for your convenience if you want to check it

Code: [Select]

if externalIP = '' then exit;
dyndns.lastIP:=externalIP;
mainfrm.setStatusBarText('Updating dynamic DNS...', 5);
s:=httpGet(AnsiReplaceStr(dyndns.url, '%ip%', externalIP));
if s > '' then dyndns.lastResult:=s;
if not mainfrm.logOtherEventsChk.checked then exit;
if length(s) > 30 then s:=intToStr(length(s))+' bytes reply'
else s:=interpretResponse(s);
mainfrm.add2log('DNS update requested for '+dyndns.lastIP+': '+s);
if not dyndns.active then
  msgDlg('DNS update failed.'#13+s+'.'#13'User intervention is required.',
    MB_ICONERROR);


[maverick]

HFS 2.1 - Build #053

As I mentioned previously, "other events" is enabled in the Log options.

I can get DNS update log activity if:

1.  I "manually" activate it with Menu > Dynamic DNS Updater > Custom > and click on OK (for the updating url that is already included there)
2.  The status bar indicates -  "Updating dynamic DNS"
3.  Screen log shows - " DNS update requested for xx.xx.x.xxx: unknown reply: " -- ?  (the ip is my correct external address)
4.  Menu > Dynamic DNS Updater > See last server response > Status=0  (which is what I was getting before for no-ip).  This response should actually show up as the DNS update reply in the screen log rather than showing unknown reply. 


And here is the HTTP activity for above:

Request Headers:
GET /rejetto/ip.php HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
User-Agent: HFS/2.1
Host: www.melauto.it

Response Headers:
HTTP/1.1 200 OK
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: PHP/4.4.1
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
Date: Sun, 29 Oct 2006 14:43:49 GMT
Connection: close
xx.xx.x.xxx

Request Headers:
GET /update.php?username=xxxxxx@xxxxxx&pass=xxxxx&host=xxxxxxxxxx&ip=xx.xx.x.xxx HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
User-Agent: HFS/2.1
Host: dynupdate.no-ip.com

Response Headers:
HTTP/1.1 200 OK
Date: Sun, 29 Oct 2006 14:43:53 GMT
Server: Apache/1.3.27 (Unix) PHP/4.3.2
X-Powered-By: PHP/4.3.2
Connection: close
Content-Type: text/html
status=0


I don't see "automatic" DNS update log events.  Therefore, I can't confirm if the DNS is updating in the background ...   I cleared my screen log.  HFS has been sitting idle with no activity for almost 2 hours.  Nothing is logged on the screen even though there should have been several DNS Updates requested during that 2 hour period.

[rejetto]

3.  Screen log shows - " DNS update requested for xx.xx.x.xxx: unknown reply: " -- ?  (the ip is my correct external address)

so, IT IS logged.

Status=0  (which is what I was getting before for no-ip).  This response should actually show up as the DNS update reply in the screen log rather than showing unknown reply.

no, it is correct. a "status=0" is not human readable. HFS correctly reports it is an unknown reply, because it doesn't know the meaning.
Anyway, there was a bug, and that's why HFS doesn't understand the reply. HFS was searching for a ":" while no-ip uses "=". Should be fixed in next version (i'm about to publish).

therefore, I can't confirm if the DNS is updating in the background ...

consider, when an error occours, it stops working.

[maverick]

so, IT IS logged.

Yes, but like I said above - ONLY - when I update manually using the routine I mentioned.  If I don't, there is NO automatic log entry to let us know if the DNS was updated.  This wasn't the behavior before.

[rejetto]

are you sure there is any dns-related non-logged http activity in the background?
maybe if nothing is logged, nothing is updated.
try using your http sniffer and see if this is true.

[maverick]

are you sure there is any dns-related non-logged http activity in the background?
maybe if nothing is logged, nothing is updated.
try using your http sniffer and see if this is true.

No doesn't look like it.  All that HFS was doing after the vfs was loaded was confirming ip's.  I logged about 5 mins when all http activity stopped and will attach the file here for you to look at.  There was nothing about DNS update.

[rejetto]

GET /ip.php HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
User-Agent: HFS/2.1a
Host: dynupdate.no-ip.com

look better.... this has nothng to do with DNS update.
it is an "external IP request" kindly made to no-ip servers: it requests ip.php
the same you can find on rejetto.com

[rejetto]

Why did you open up a deleted post and quote from it anyway?

sometimes i open the posts and reply offline, posting when i'm connected again. i'm not home.
didn't notice the edit, just looked for new posts.

so.... is there any supposed bug in the DNS updater?

[rejetto]

i don't understand the problem.
the activity should be only
1) when you configure the service, and
2) when the external IP changes.
if neither 1 or 2 happens, you can wait for days, and no activity is required.
so, your report seems to be ok, not showing a bug.

[maverick]

No bug for no-ip.  DNS updates correctly when there is a IP change.