myownb3.com problems

[elsbernd]

Hello MouettE,
Hope you're doing well.

It seems, that the easyfind.pl on my old b3 tries to update trippstadt.myownb3.com to the IP-address to 88.180.91.xyz, but the address points still to 209.99.40.222.
nslookup trippstadt.myownb3.com
Server: 192.168.178.17
Address: 192.168.178.17#53

Non-authoritative answer:
Name: trippstadt.myownb3.com
Address: 209.99.40.222

This IP-address belongs to 209-99-40-222.fwd.datafoundry.com and not to my provider.
Question: Is easyfind still working (with the old excito-bundled OS)?

[Gordon]

It's becoming harder to support older encryption methods with every upgrade of openssl and they have been quite active the last months. I have in fact had some local breakages as well on account of a self-signed certificate that I use for my email server and apparently is now considered unsafe because a brute-force attack might succeed in some 50-100 years. Yeah, that really bothers me as a person who will no longer be around by then. I suppose that to prevent a future full blockage it's better to update the keys now though - is there any specific reason why you would not consider bending?

[josvergeer]

Hello,
I have the same problem.
I got to a site it is called "myownb3.com".
See attached file.
I hope you can do anything with it.
Jos

[Gordon]

Yep. Something is definitely broken:

Code: Select all

; <<>> DiG 9.16.30 <<>> ns myownb3.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51900
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;myownb3.com.			IN	NS

;; AUTHORITY SECTION:
myownb3.com.		600	IN	SOA	ns1.verification-hold.suspended-domain.com. admin.suspended-domain.com. 2012022012 7200 7200 172800 7200