Mailing List Archive

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> http://gabrielmartin.net/projects/hipku/

Something's wrong here....

bjorn@canardo:~$ dig aaaa gabrielmartin.net

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> aaaa gabrielmartin.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11617
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;gabrielmartin.net. IN AAAA

;; AUTHORITY SECTION:
gabrielmartin.net. 1708 IN SOA ns1.digitalocean.com. hostmaster.gabrielmartin.net. 1418739098 10800 3600 604800 1800

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Dec 16 20:53:16 2014
;; MSG SIZE rcvd: 102



Bjørn

DigitalOcean only has IPv6 in Singapore so far (AFAIK)

-Grant

On Tue, Dec 16, 2014 at 11:54 AM, Bjørn Mork <bjorn@mork.no> wrote:
>
> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>
> > http://gabrielmartin.net/projects/hipku/
>
> Something's wrong here....
>
> bjorn@canardo:~$ dig aaaa gabrielmartin.net
>
> ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> aaaa gabrielmartin.net
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11617
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;gabrielmartin.net. IN AAAA
>
> ;; AUTHORITY SECTION:
> gabrielmartin.net. 1708 IN SOA ns1.digitalocean.com.
> hostmaster.gabrielmartin.net. 1418739098 10800 3600 604800 1800
>
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Tue Dec 16 20:53:16 2014
> ;; MSG SIZE rcvd: 102
>
>
>
> Bjørn
>

They now have it in their NYC3 datacenter also.

Robert

On Tue, 16 Dec 2014 14:33:03 -0800
Grant Ridder <shortdudey123@gmail.com> wrote:
> DigitalOcean only has IPv6 in Singapore so far (AFAIK)
>
> -Grant
>
> On Tue, Dec 16, 2014 at 11:54 AM, Bjørn Mork <bjorn@mork.no> wrote:
>>
>> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>>
>> > http://gabrielmartin.net/projects/hipku/
>>
>> Something's wrong here....
>>
>> bjorn@canardo:~$ dig aaaa gabrielmartin.net
>>
>> ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> aaaa gabrielmartin.net
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11617
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;gabrielmartin.net. IN AAAA
>>
>> ;; AUTHORITY SECTION:
>> gabrielmartin.net. 1708 IN SOA
>> ns1.digitalocean.com.
>> hostmaster.gabrielmartin.net. 1418739098 10800 3600 604800 1800
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 127.0.0.1#53(127.0.0.1)
>> ;; WHEN: Tue Dec 16 20:53:16 2014
>> ;; MSG SIZE rcvd: 102
>>
>>
>> Bjørn
>>

On 12/16/2014 11:33 PM, Grant Ridder wrote:
> DigitalOcean only has IPv6 in Singapore so far (AFAIK)

No, NYC3, AMS3, SGP1, LON1

On Tue, Dec 16, 2014 at 11:35:33PM +0100, Dominik Bay wrote:
> On 12/16/2014 11:33 PM, Grant Ridder wrote:
> > DigitalOcean only has IPv6 in Singapore so far (AFAIK)
>
> No, NYC3, AMS3, SGP1, LON1

Interestingly they don't currently support *outbound* IPv6 SMTP (at
least from LON1) and have no ETA for when they might. Outbound IPv6 SSH
works fine, as does inbound IPv6 SMTP/SSH. Not entirely clear on the
logic there.

J.

--
"This sentence no verb." -- Robin Stevens, ox.talk
This .sig brought to you by the letter G and the number 33
Product of the Republic of HuggieTag

On 17/12/14 11:58, Jonathan McDowell wrote:
> Interestingly they don't currently support *outbound* IPv6 SMTP (at
> least from LON1) and have no ETA for when they might.

By ‘support’ do you mean ‘allow’? (*)

--
(*) Also known in some circles as ‘not blocking’, although this usage is somewhat controversial, pending an RFC publication.

On 2014-12-16 20:54, Bjørn Mork wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com> writes:
>
>> http://gabrielmartin.net/projects/hipku/
>
> Something's wrong here....
>
> bjorn@canardo:~$ dig aaaa gabrielmartin.net

Yeah, always silly folks who still don't have AAAA on their sites...

Seem it uses the javascript from:
http://www.telize.com/jsonip?callback=init

Great way to have that site inject arbitrary javascript into your page...

That one does have IPv6:
$ dig +short www.telize.com aaaa
2a02:2770:9:0:21a:4aff:feed:aa95

and that is where the 'your ip' gets your IP from, which might be IPv6,
or on the next reload IPv4 or on the next reload something else
depending on the location of the moon and how much air you puff into the
sky... long live happy eyeballs..

Greets,
Jeroen

On Wed, Dec 17, 2014 at 02:23:32PM +1100, Jeremy Visser wrote:
> On 17/12/14 11:58, Jonathan McDowell wrote:
> > Interestingly they don't currently support *outbound* IPv6 SMTP (at
> > least from LON1) and have no ETA for when they might.
>
> By ‘support’ do you mean ‘allow’? (*)

Outbound IPv6 connections to port 25 time out and the statement from
Digital Ocean was "Unfortunately, at this time, we do not allow SMTP
over IPv6.".

> --
> (*) Also known in some circles as ‘not blocking’, although this usage
> is somewhat controversial, pending an RFC publication.

J.

--
Life would be easier if I had | .''`. Debian GNU/Linux Developer
the source code. | : :' : Happy to accept PGP signed
| `. `' or encrypted mail - RSA
| `- key on the keyservers.

On 12/17/2014 06:29, Jonathan McDowell wrote:
> Outbound IPv6 connections to port 25 time out and the statement from
> Digital Ocean was "Unfortunately, at this time, we do not allow SMTP
> over IPv6.".

They are also blocking outbound port 587 (submission) which I found out
the hard way when mail was being delayed as Postfix tried IPv6 and timed
out.

When I asked them about it:
"Hi there,

Thanks so much for contacting us regarding SMTP on IPv6. At this time
we've blocked SMTP by default. We suggest using an IPv4 droplet to gain
SMTP access.

The reason behind this is that it's a new feature on DigitalOcean and
we're easing into the roll out of the feature. We appreciate your
understanding on this. Please let us know if you have any questions.

Thank you,
DigitalOcean Support"

--
staticsafe
https://staticsafe.ca

Is it possible because they can't easily assign PTRs to their IPv6 address space?

Frank

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de] On Behalf Of staticsafe
Sent: Wednesday, December 17, 2014 2:37 PM
To: ipv6-ops@lists.cluenet.de
Subject: Re: New operational tool

On 12/17/2014 06:29, Jonathan McDowell wrote:
> Outbound IPv6 connections to port 25 time out and the statement from
> Digital Ocean was "Unfortunately, at this time, we do not allow SMTP
> over IPv6.".

They are also blocking outbound port 587 (submission) which I found out
the hard way when mail was being delayed as Postfix tried IPv6 and timed
out.

When I asked them about it:
"Hi there,

Thanks so much for contacting us regarding SMTP on IPv6. At this time
we've blocked SMTP by default. We suggest using an IPv4 droplet to gain
SMTP access.

The reason behind this is that it's a new feature on DigitalOcean and
we're easing into the roll out of the feature. We appreciate your
understanding on this. Please let us know if you have any questions.

Thank you,
DigitalOcean Support"

--
staticsafe
https://staticsafe.ca

On Wed, Dec 17, 2014 at 09:58:19PM -0600, Frank Bulk wrote:
> Is it possible because they can't easily assign PTRs to their IPv6
> address space?

Their system automatically assigns a PTR to the initial IPv6 address in
the same manner as for the IPv4 address. I'm not sure about the ability
to assign a PTR to any further v6 addresses that are used though.

> -----Original Message-----
> From: ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com@lists.cluenet.de] On Behalf Of staticsafe
> Sent: Wednesday, December 17, 2014 2:37 PM
> To: ipv6-ops@lists.cluenet.de
> Subject: Re: New operational tool
>
> On 12/17/2014 06:29, Jonathan McDowell wrote:
> > Outbound IPv6 connections to port 25 time out and the statement from
> > Digital Ocean was "Unfortunately, at this time, we do not allow SMTP
> > over IPv6.".
>
> They are also blocking outbound port 587 (submission) which I found out
> the hard way when mail was being delayed as Postfix tried IPv6 and timed
> out.

J.

--
I'm not popular enough to be different.