OpenSSL 1.0 will continue to be supported. There's no rush to go to 1.1 release.
I can't see this as an issue.
Sent from my iPhone
> On Aug 17, 2016, at 23:38, The Doctor wrote:
>
>> On Thu, Aug 18, 2016 at 12:13:29PM +1000, Mark Andrews wrote:
>>
>> In message , The Doctor writes:
>>> Questi
In article ,
"Darcy Kevin (FCA)" wrote:
> Barry,
> Cloudflare has been doing this for a while, so that their customers
> won't be
> "limited by the DNS specifications (RFCs)" . Having done that,
> they were compelled to offer another service -- so-called "CNAME flattening"
> -- to fix
On Thu, Aug 18, 2016 at 12:13:29PM +1000, Mark Andrews wrote:
>
> In message , The Doctor writes:
> > Question, Is Bind openssl 1.1 ready?
>
> No. OpenSSL 1.1 breaks the build. They take things away with no
> viable alternatives as of last - 1 snapshot.
>
Openssl is aiming for a 26 Aug 2016 re
In message , The Doctor writes:
> Question, Is Bind openssl 1.1 ready?
No. OpenSSL 1.1 breaks the build. They take things away with no
viable alternatives as of last - 1 snapshot.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742
Hi Kevin
Does that mean I setup another forwarding zone called microsoft.com or
sharepoint.microsoft.com or both?
And then do i need to add NS record entries similar to sharepoint.com in the
fake root file?
Regards
Anup
From: anup albal
Sent: Thursday, 18
Hi Chris
Below is without "+trace" option. Also there is a firewall between internal
(dns1) and external (ns1) name servers and
we have opened up TCP/UDP port 53 from dns1 to ns1.
; <<>> DiG 9.3.4-P1 <<>> sharepoint.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY
Barry,
Cloudflare has been doing this for a while, so that their customers
won't be "limited by the DNS specifications (RFCs)" . Having done
that, they were compelled to offer another service -- so-called "CNAME
flattening" -- to fix the brokenness that's caused by their base offering.
In article ,
"Darcy Kevin (FCA)" wrote:
> Well, sharepoint.com is a CNAME to sharepoint.microsoft.com, so you might
> need to make arrangements for that to be resolvable as well.
That doesn't seem valid to begin with. The .COM zone has delegation NS
records for sharepoint.com. Having a CNAME
Well, sharepoint.com is a CNAME to sharepoint.microsoft.com, so you might need
to make arrangements for that to be resolvable as well.
Try it without "+trace".
Regards,
Chris
> On Aug 17, 2016, at 2:59 AM, anup albal wrote:
>
> Hi
>
> First up apologies if this is not the right list to email and for a long
> email. I am hoping you can give me a clue as to what I am doing wrong here?
> Or may be this is not supposed to work
Doctor,
I enjoyed how http://www.gizoogle.net/textilizer.php adjusted your sig:
Member - Liberal International
God, Queen n' ghetto dag! Never Satan Prezzy Republic! Beware AntiChrist
rising!
Look at Psalms 14 n' 53 on Atheism
Time fo' tha USA ta hold a referendum on its rehood n' vote ta di
Question, Is Bind openssl 1.1 ready?
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
Time for the USA to hold
Hi
First up apologies if this is not the right list to email and for a long email.
I am hoping you can give me a clue as to what I am doing wrong here? Or may be
this is not supposed to work at all.
We have an internal only DNS server (dns1) with fake root zone. i.e a fake file
for the zone ".
13 matches
Mail list logo
