easyfind not working

[Nrde]

does easyfind work for anyone?

I have had B3 for a while but only now started to use easyfind service of my b3. For soem reason it does not work at all. ping to my easyfind address returns:

Ping request could not find host nrdehost.myownb3.com. Please check the name and try again.

Is there a way to see if the service is running and is there some services that need to be running for it work? (I disabled some cron jobs at one point because they supposedly helped for small stability issues I was having).

[Cheeseboy]

Hi Nrde,

I have never used it before, but I enabled it just now to test, and yes it works:

Code: Select all

xyz@b3:~$ nslookup cheeseboy.myownb3.com
Server:		192.168.10.1
Address:	192.168.10.1#53

Non-authoritative answer:
Name:	cheeseboy.myownb3.com
Address: 94.254.65.124

Yours however does not:

Code: Select all

xyzs@b3:~$ nslookup nrdehost.myownb3.com
Server:		192.168.10.1
Address:	192.168.10.1#53

** server can't find nrdehost.myownb3.com: NXDOMAIN

All I did was to enable it in the web interface.
What did you disable?

Best regards,

Cheeseboy

EDIT:
I disabled it, then enabled it again to check from an external site. Now it doesn't work, even internal dnsmasq doesn't recognize the name... But as there is no TTL setting, who knows how long it will take to reflect?

[Ubi]

Either I completely misunderstand how this magical easyfind works but it seems to be a dynamic DNS updater. In this case all names are under myownb3.com. So let's go via the tree and not rely on local services.

Code: Select all

[joris@junction ~]$ dig -t NS +short +answer myownb3.com
ns1.excito.org.
ns2.excito.org.

so I guess the dynamic updater is hosted by excito. Next step is to ask questions directly at the authoritive source to minimize external issues while debugging this problem:

Code: Select all

[joris@junction ~]$ dig @ns1.excito.org cheeseboy.myownb3.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @ns1.excito.org cheeseboy.myownb3.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23779
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;cheeseboy.myownb3.com.         IN      A

;; AUTHORITY SECTION:
myownb3.com.            600     IN      SOA     ns1.excito.org. info.excito.com. 489 600 300 604800 600

Indeed, no data for this host. My own B3 is currently offline so I cannot test, but maybe this code may help you debugging your problems.

[beweb]

Hi,

Had the same problem. For me it worked to just disable the service, waited for the confirmation at the bottom of the page, and then started it again.
After that it worked.

[Ubi]

not really. I'm getting

Code: Select all

Failed to connect to database.
Server responded: Failed to connect to database server

.
My guess would be some issue at the easyfind server @excito. Oddly when I do get an "update successful" it still doesn;t work (except for the very first time).

[Ubi]

oh wait now it does work! Something is a bit flaky somewhere

[johannes]

So does this work for everyone now? Let us know otherwise!

Best,

[Ubi]

it seems to work sometimes, rather than some-persons

[johannes]

Really, are you sure? I use it all the time and for me it's stable. Not just dns propagation issues?

Thanks,

[Ubi]

as you notice above I poll the authoritative NS directly. Do you turn on/off your easyfind regularly johannes? It seems that is were the problems are.

[johannes]

Hmm, right. I'll do some stress-testing and see what happens. Thanks.

[Nrde]

I tried to disable and enable my easyfind name. Everything seems to be fine on the UI but syslog shows the following:

May 28 11:17:28 b3 bubba-networkmanager: Server timed out, terminating
May 28 11:17:28 b3 bubba-networkmanager: Daemon terminating
May 28 11:17:28 b3 bubba-networkmanager: Shutting down

Also my hostname does not appear to be anywhere...

[Cheeseboy]

I get those precise messages as well every now and then.
I don't think they are related to your easyfind settings, as they have had absolutely no effect for me, and I'm not using easyfind.

What do you mean your hostname does not appear anywhere?

Code: Select all

# grep -r <external hostname> /etc/*
# grep -r <external hostname> /var/log/*

Best regards,

Niklas

[Nrde]

What do you mean your hostname does not appear anywhere?

Code: Select all

# grep -r <external hostname> /etc/*
# grep -r <external hostname> /var/log/*

I meant for example ping was not able to find it. But it might have been just a delay when updating the DNS servers as now I can see my hostname. I just have to resist making any changes and risking it breaking again

[Ron]

I had the same:
easyfind was not working,
in admin put it off and on, updated,
easyfind worked again.