Re: [opennic-discuss] Please add .epic to your servers!2a02:a00:2000:3b::2

This is a multi-part message in MIME format...

------------=_1567910483-2199-16
Content-Type: text/plain; charset="UTF-8"

Is updated: .epic

- a.dns.anonymous.support
ns19.de.dns.opennic.glue -> 217.144.132.148 -> 2a02:a00:2000:22::1

- b.dns.anonymous.support
ns25.de.dns.opennic.glue -> 217.144.135.7 -> 2a02:a00:2000:22::2

- c.dns.anonymous.support
ns26.de.dns.opennic.glue -> 217.144.132.169 -> 2a02:a00:2000:3b::1

- d.dns.anonymous.support
ns27.de.dns.opennic.glue -> 217.144.135.2 -> 2a02:a00:2000:3b::2


2019-09-07 12:43 GMT+02:00, Timothy Rogers <[email protected]>:
> Thank you for the heads up, I will update the playbooks for OpenNIC Ansible
> setup. As far as scripting a way to keep them updated without having to
> re-run an updated playbook, I would be happy to hear suggestions.
>
> Timothy Francis Rogers
> [email protected]
> On Sep 6, 2019, 2:36 PM -0400, Jeff Taylor <[email protected]>, wrote:
>> It looks like a large number of T1 and T2 servers are no longer using
>> any kind of scripting to update their information when opennic's TLD
>> information changes.  Please note the recent addition of .epic hosted
>> from ns13.opennic.glue (144.76.103.143).
>>
>>
>>
>> --------
>> You are a member of the OpenNIC Discuss list.
>> You may unsubscribe by emailing
>> [email protected]
>

------------=_1567910483-2199-16
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit



--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing [email protected]

------------=_1567910483-2199-16--