This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Deletion of ns-v6.ripe.net
- Previous message (by thread): [dns-wg] Deletion of ns-v6.ripe.net
- Next message (by thread): [dns-wg] Deletion of ns-v6.ripe.net
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anand Buddhdev
anandb at ripe.net
Tue Apr 24 17:07:41 CEST 2018
On 24/04/2018 16:48, Jim Reid wrote: Hi Jim, > Anand, could you clarify what you mean by “no longer in use”? Has it > gone from all the reverse zones that referenced it? Are no more queries > for ns-v6.ripe.net hitting the ripe.net name servers? There are no domain objects in the RIPE Database, with "ns-v6.ripe.net" in their "nserver" attributes. The domains that are using "ns.ripe.net", when queried for NS records, only return "ns.ripe.net" and not "ns-v6.ripe.net". Checking for queries for "ns-v6.ripe.net" on the all the ripe.net name servers isn't possible, because we don't have access to query logs of the servers that provide us with secondary DNS service. Even if we *could* look at the queries, and they showed queries for "ns-v6.ripe.net", it doesn't mean that the name is in use. > I’m wondering if the name might still be hard-wired into scripts or > provisioning/testing tools. It may be hard-wired in some scripts, and if so, they may produce an error. However, it is not used as the target of any NS records that we are aware of, so I don't expect any major outages. Regards, Anand
- Previous message (by thread): [dns-wg] Deletion of ns-v6.ripe.net
- Next message (by thread): [dns-wg] Deletion of ns-v6.ripe.net
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]