On Jan 17, 2019, at 20:11, Michael Sinatra wrote:
>
> I suspect the freebsd.org hostmaster will probably want to drop a line to ISC.
I’ve gotten a response from the dnsadm@ folks, who will follow up with the ISC
folks.
Not many people know about this it seems:
I have already forwarded the email to clusteradm@.
mcl
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 1/17/19 4:42 PM, George Mitchell wrote:
> On 1/17/19 6:55 PM, David Magda wrote:
>> Hello,
>>
>> On February 1, 2019, there will be some major changes to DNS with regards to
>> EDNS:
>> [...]
>> It turns out that freebsd.org is effected by this:
>> [...]
>> Who is the person that should be
Which then tells me to go to dnsadm@. Thanks.
> On Jan 17, 2019, at 19:42, George Mitchell wrote:
>
> On 1/17/19 6:55 PM, David Magda wrote:
>> Hello,
>>
>> On February 1, 2019, there will be some major changes to DNS with regards to
>> EDNS:
>> [...]
>> It turns out that freebsd.org is
On 1/17/19 6:55 PM, David Magda wrote:
> Hello,
>
> On February 1, 2019, there will be some major changes to DNS with regards to
> EDNS:
> [...]
> It turns out that freebsd.org is effected by this:
> [...]
> Who is the person that should be looking at this for FreeBSD?
> [...]
According to
Hello,
On February 1, 2019, there will be some major changes to DNS with regards to
EDNS:
> A number of DNS software and service providers have announced that we will
> all cease implementing DNS resolver workarounds to accommodate DNS
> authoritative systems that don’t follow the EDNS
Click here to add text.
http://vectorart68102.acemlnb.com/lt.php?s=6ed67b7e45a259d665604a273cf14132=18A54A1A196
Greetings from Team Vector Art! A team or Promotional Products
specialists of Vector, Total Creative Solution's & Digitizing Team. Am
opportunity to work on Virtual Proof / Mock up &
so, having got a workaround for yesterdays problems, I now went to upgrade my
other pair of boxes using CARP. No 'pf' on these, just one shared address.
This is the setup I have tested in development and it works fine.
I install the new kenel and do the first reboot - and I get the panic
below.
