- Dillo-dev - lists.mailman3.com

[patch] HTML parser bugfix

by onepoint＠starurchin.org

123 wrote: > On Sun, Jun 03, 2012 at 09:00:55PM +0100, Jeremy Henty wrote: > > If you don't detect and ignore that extra double quote you will > > break many pages that every other browser renders perfectly well. > > Then there should be some logic for detecting double quotes. I agree. The hard question is: what logic? > Searching for < inside quotes is not the right way as it breaks > valid pages like reddit main page. Again, I agree. In fact, I decided to experiment with removing Dillo's misquote-detection just because it broke reddit. Unfortunately it is very hard to come up with an algorithm that correctly handles the various quoting horrors that you see all the time, yet also correctly parses embedded javascript fragments like: onclick='alert("clicked")' (IIRC Dillo mis-renders reddit because of embedded javascript like this.) > Can you give examples of real web pages with double quotes? I have attached a bunch of links that I collected after spending a lot of time debugging pages that broke my locally-patched Dillo. (Ignore the file:///... URLs as they obviously won't work for you.) I have also attached the two patches I use. I think the first does the same thing that you propose, although I haven't checked that in detail. The second attempts to copy Firefox's misquote-detection algorithm. I agree that Dillo's misquote-detection isn't good enough, but just taking it out is a step backwards, and it is a mistake to propose changes to it based solely on particular pages that Dillo mis-renders, because any such change needs to be tested against the many other broken pages that Dillo currently renders more or less correctly. Regards, Jeremy Henty

June 6, 2012

dillo.org web site

by jcid＠dillo.org

[here goes the attachement] -- Cheers Jorge.-

June 6, 2012

dillo.org web site

by jcid＠dillo.org

On Tue, Jun 05, 2012 at 02:52:08PM -0800, Roger wrote: > > On Tue, Jun 05, 2012 at 02:03:12PM -0400, Jorge Arellano Cid wrote: > >On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: > >> > >> Jorge Arellano Cid wrote: > >> > >> > The domain was renewed, but I still can't see the website from > >> > Chile, although when I log to the wearlab it works [1]. > >> > >> Using dillo, Firefox and links, www.dillo.org works but dillo.org > >> returns nothing but some <script> elements from sedoparking.com . > > > > It doesn't work here... :( > > > > Yesterday I filled a "Case management" ticket at dotster > >(000domains.com) 24 hours have passed and not even a single > >automated answer has come from them. > > > > Can someone in the US please help us with this? There's a phone > >number to call 800-401-5220. The case ticket number is 01278137. > >If somebody volunteers please write me to send you the account > >credentials. > > Any takers? I can do so, but I don't want to duplicate efforts, as it might > look suspicious with more then two people calling in. Today I login into 000domains to see what happened with the ticket and to my surprise there's an internal error message saying they can't access my case management ticket (this is the attachment). This message gives a different phone number to call [1]. @Roger (or any volunteer): Can you please call this number and ask what the problem is. [1] +1 360-253-2210 Another way to solve the problem may be to point to a working nameserver elsewhere too (the API seems to allow this option). I'll ask Andreas K. whether we can point to the wearlab DNS in the interim. -- Cheers Jorge.-

June 6, 2012

dillo.org web site

by rogerx.oss＠gmail.com

> On Tue, Jun 05, 2012 at 02:03:12PM -0400, Jorge Arellano Cid wrote: >On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: >> >> Jorge Arellano Cid wrote: >> >> > The domain was renewed, but I still can't see the website from >> > Chile, although when I log to the wearlab it works [1]. >> >> Using dillo, Firefox and links, www.dillo.org works but dillo.org >> returns nothing but some <script> elements from sedoparking.com . > > It doesn't work here... :( > > Yesterday I filled a "Case management" ticket at dotster >(000domains.com) 24 hours have passed and not even a single >automated answer has come from them. > > Can someone in the US please help us with this? There's a phone >number to call 800-401-5220. The case ticket number is 01278137. >If somebody volunteers please write me to send you the account >credentials. Any takers? I can do so, but I don't want to duplicate efforts, as it might look suspicious with more then two people calling in. Probably should have privately emailed some of us first, then sent a public email, unless you've already tried calling too. Well called anyways and it appears to be a Mexico or South American based phone number and not a US one based on the language used. The girl answering the phone does sound really pretty, but my hispanol (spanish) is a little rough here. Depressing. ;-) I'm sure this will provoke some interest with the rest of you guys calling the number too. -- Roger http://rogerx.freeshell.org/

June 5, 2012

dillo.org web site

by jcid＠dillo.org

On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: > > Jorge Arellano Cid wrote: > > > The domain was renewed, but I still can't see the website from > > Chile, although when I log to the wearlab it works [1]. > > Using dillo, Firefox and links, www.dillo.org works but dillo.org > returns nothing but some <script> elements from sedoparking.com . It doesn't work here... :( Yesterday I filled a "Case management" ticket at dotster (000domains.com) 24 hours have passed and not even a single automated answer has come from them. Can someone in the US please help us with this? There's a phone number to call 800-401-5220. The case ticket number is 01278137. If somebody volunteers please write me to send you the account credentials. <ticket text> Hi, I've been using the service for 12 years. I renewed the service on June 01, after a few days it expired (May 28). Today is June 04, and DNS management doesn't work. It points to a parking place. jcid at infinity:~$ nslookup www.dillo.org ns1.nameresolve.com Server: ns1.nameresolve.com Address: 66.96.142.146#53 Name: www.dillo.org Address: 63.251.171.80 Name: www.dillo.org Address: 66.150.161.141 Name: www.dillo.org Address: 134.102.206.165 Name: www.dillo.org Address: 69.25.27.173 Name: www.dillo.org Address: 66.150.161.140 Name: www.dillo.org Address: 69.25.27.170 Name: www.dillo.org Address: 63.251.171.81 TIA. </ticket text> -- Cheers Jorge.-

June 5, 2012

dillo.org web site

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > The domain was renewed, but I still can't see the website from > Chile, although when I log to the wearlab it works [1]. Using dillo, Firefox and links, www.dillo.org works but dillo.org returns nothing but some <script> elements from sedoparking.com . dnsip returns the same result for dillo.org and www.dillo.org: 134.102.206.165 63.251.171.80 63.251.171.81 66.150.161.140 66.150.161.141 69.25.27.170 69.25.27.173 Regards, Jeremy Henty

June 5, 2012

[patch] dlib cleanup

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > Some C libs leave errno unset, and others always set it to ENOMEM. > Please excuse my ignorance, but what other error conditions may > malloc return? According to the man pages on my Linux system: The Unix98 standard requires malloc(), calloc(), and realloc() to set errno to ENOMEM upon failure. Glibc assumes that this is done (and the glibc versions of these routines do this); if you use a private malloc implementation that does not set errno, then certain library routines may fail with- out having a reason in errno. So, unless we support systems that do not conform to Unix98, then I read this as saying that ENOMEM is the only error we will see. Regards, Jeremy Henty

June 5, 2012

dillo.org web site

by rogerx.oss＠gmail.com

> On Mon, Jun 04, 2012 at 12:26:07PM -0400, Jorge Arellano Cid wrote: >Hi there, > > The domain was renewed, but I still can't see the website from Chile, >although when I log to the wearlab it works [1]. > > Is everybody seeing having the same problem? Blank white page here in Alaska. whois shows the address as owned by Jorg. Mon Jun 4 19:21:52 AKDT 2012 -- Roger http://rogerx.freeshell.org/

June 5, 2012

dillo.org web site

by higuita7＠yahoo.co.uk

Hi > > in whois, hence I assume it is just a DNS configuration issue?! > Hmmm, the DNS is managed by the same provider [1]. yep, its a DNS problem, the domain points to the nameresolve.com dns servers and they are pointing both the www and the domain to the default parking pages and to the IP 134.102.206.165 (the correct page) So you have to make sure that the domain only have one A record for those entries, and if its already just one A record, its probably a bug in the nameresolve.com, that didnt removed the dns parking entries from the domain. ~/$ dnstracer -s . www.dillo.org -o Tracing to www.dillo.org[a] via A.ROOT-SERVERS.NET, maximum of 3 retries A.ROOT-SERVERS.NET [.] (2001:0503:ba3e:0000:0000:0000:0002:0030) |\___ b0.org.afilias-nst.org [org] (2001:0500:000c:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) Got authoritative answer | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) Got authoritative answer | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) Got authoritative answer | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) Got authoritative answer |\___ b0.org.afilias-nst.org [org] (199.19.54.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ a2.org.afilias-nst.info [org] (2001:0500:0040:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a2.org.afilias-nst.info [org] (199.249.112.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (2001:0500:000e:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (199.19.56.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ c0.org.afilias-nst.info [org] (2001:0500:000b:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ c0.org.afilias-nst.info [org] (199.19.53.1) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ d0.org.afilias-nst.org [org] (2001:0500:000f:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ d0.org.afilias-nst.org [org] (199.19.57.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ b2.org.afilias-nst.org [org] (2001:0500:0048:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) \___ b2.org.afilias-nst.org [org] (199.249.120.1) |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 69.25.27.173 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 63.251.171.81 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 66.150.161.140 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 134.102.206.165 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 66.150.161.141 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 69.25.27.170 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 63.251.171.80 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 66.150.161.140 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 69.25.27.170 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 63.251.171.80 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 69.25.27.173 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 66.150.161.141 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 69.25.27.173 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 66.150.161.140 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 134.102.206.165 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 66.150.161.141 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 69.25.27.170 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 63.251.171.80 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 66.150.161.140 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 69.25.27.170 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 134.102.206.165 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 63.251.171.80 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 69.25.27.173 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 66.150.161.141 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 63.251.171.81 ~/$ dnstracer -s . dillo.org -o Tracing to dillo.org[a] via A.ROOT-SERVERS.NET, maximum of 3 retries A.ROOT-SERVERS.NET [.] (2001:0503:ba3e:0000:0000:0000:0002:0030) |\___ d0.org.afilias-nst.org [org] (2001:0500:000f:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) Got authoritative answer | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) Got authoritative answer | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) Got authoritative answer | \___ ns3.nameresolve.com [dillo.org] (66.96.142.148) Got authoritative answer |\___ d0.org.afilias-nst.org [org] (199.19.57.1) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ b0.org.afilias-nst.org [org] (2001:0500:000c:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) |\___ b0.org.afilias-nst.org [org] (199.19.54.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (2001:0500:000e:0000:0000:0000:0000:0001) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) |\___ a0.org.afilias-nst.info [org] (199.19.56.1) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ c0.org.afilias-nst.info [org] (2001:0500:000b:0000:0000:0000:0000:0001) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ c0.org.afilias-nst.info [org] (199.19.53.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | \___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ b2.org.afilias-nst.org [org] (2001:0500:0048:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ b2.org.afilias-nst.org [org] (199.249.120.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a2.org.afilias-nst.info [org] (2001:0500:0040:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) \___ a2.org.afilias-nst.info [org] (199.249.112.1) |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) ns3.nameresolve.com (66.96.142.148) dillo.org -> 66.150.161.141 ns3.nameresolve.com (66.96.142.148) dillo.org -> 69.25.27.170 ns3.nameresolve.com (66.96.142.148) dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) dillo.org -> 66.150.161.140 ns3.nameresolve.com (66.96.142.148) dillo.org -> 63.251.171.80 ns3.nameresolve.com (66.96.142.148) dillo.org -> 69.25.27.173 ns3.nameresolve.com (66.96.142.148) dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) dillo.org -> 66.150.161.141 ns2.nameresolve.com (65.254.254.170) dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) dillo.org -> 69.25.27.170 ns2.nameresolve.com (65.254.254.170) dillo.org -> 69.25.27.173 ns2.nameresolve.com (65.254.254.170) dillo.org -> 66.150.161.140 ns2.nameresolve.com (65.254.254.170) dillo.org -> 63.251.171.81 ns2.nameresolve.com (65.254.254.170) dillo.org -> 63.251.171.80 ns1.nameresolve.com (66.96.142.146) dillo.org -> 63.251.171.80 ns1.nameresolve.com (66.96.142.146) dillo.org -> 66.150.161.140 ns1.nameresolve.com (66.96.142.146) dillo.org -> 134.102.206.165 ns1.nameresolve.com (66.96.142.146) dillo.org -> 66.150.161.141 ns1.nameresolve.com (66.96.142.146) dillo.org -> 69.25.27.170 ns1.nameresolve.com (66.96.142.146) dillo.org -> 69.25.27.173 ns1.nameresolve.com (66.96.142.146) dillo.org -> 63.251.171.81 ns4.nameresolve.com (65.254.254.172) dillo.org -> 66.150.161.141 ns4.nameresolve.com (65.254.254.172) dillo.org -> 63.251.171.81 ns4.nameresolve.com (65.254.254.172) dillo.org -> 69.25.27.173 ns4.nameresolve.com (65.254.254.172) dillo.org -> 69.25.27.170 ns4.nameresolve.com (65.254.254.172) dillo.org -> 66.150.161.140 ns4.nameresolve.com (65.254.254.172) dillo.org -> 134.102.206.165 ns4.nameresolve.com (65.254.254.172) dillo.org -> 63.251.171.80 higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

June 4, 2012

dillo.org web site

by jcid＠dillo.org

HI, On Mon, Jun 04, 2012 at 06:53:06PM +0200, Axel Beckert wrote: > Hi, > > On Mon, Jun 04, 2012 at 12:26:07PM -0400, Jorge Arellano Cid wrote: > > The domain was renewed, but I still can't see the website from Chile, > > although when I log to the wearlab it works [1]. > > > > Is everybody seeing having the same problem? > > > > [1] lynx www.dillo.org > > Looks fishy from here in Switzerland. I get the same DNS entries as > Sebastian and they seem to point to some Domain parking page by the > well-known domain broker Sedo with only advertisement links on it. > > But "whois dillo.org" states that the domain belongs to Jorge. Henning wrote: > I am getting a placeholder ad/spam-link page. You are still registered > in whois, hence I assume it is just a DNS configuration issue?! Hmmm, the DNS is managed by the same provider [1]. Well, dotster uses four DNS servers: ns[1-4].nameresolve.com and here I get: jcid at infinity:~$ nslookup www.dillo.org ns1.nameresolve.com Server: ns1.nameresolve.com Address: 66.96.142.146#53 Name: www.dillo.org Address: 63.251.171.80 Name: www.dillo.org Address: 66.150.161.141 Name: www.dillo.org Address: 134.102.206.165 Name: www.dillo.org Address: 69.25.27.173 Name: www.dillo.org Address: 66.150.161.140 Name: www.dillo.org Address: 69.25.27.170 Name: www.dillo.org Address: 63.251.171.81 so it looks like I should contact them... [1] http://www.dotster.com/domains/tools.bml -- Cheers Jorge.-

June 4, 2012