* sourceware move
@ 2020-02-03 19:16 Frank Ch. Eigler
2020-02-04 2:46 ` Ian Lance Taylor
0 siblings, 1 reply; 4+ messages in thread
From: Frank Ch. Eigler @ 2020-02-03 19:16 UTC (permalink / raw)
To: Sourceware Overseers
Hi -
I am planning to spend a chunk of this current year's current month in
getting sourceware.org moved over to the new hardware (also sponsored
by Red Hat) at our RDU data center.
I plan to track progress generally at this here wiki page, and will
chat nonstop on #overseers IRC.
https://sourceware.org/sourceware-wiki/MigrationWorkItems/
I'd appreciate a fanout of the news of the likely weekend-ish outage
when the final switchover is done, probably toward the end of month.
Just please prep your communities at this time.
I'd appreciate contact from the dns owner for sourceware.org (ian?) to
arrange the needed NS changes. We may be able to set up transitional
records there immediately. The key is adding an NS record that points
to server2.sourceware.org, which eventually would become the primary.
- FChE
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sourceware move
2020-02-03 19:16 sourceware move Frank Ch. Eigler
@ 2020-02-04 2:46 ` Ian Lance Taylor
2020-02-04 2:53 ` Frank Ch. Eigler
0 siblings, 1 reply; 4+ messages in thread
From: Ian Lance Taylor @ 2020-02-04 2:46 UTC (permalink / raw)
To: Frank Ch. Eigler; +Cc: Sourceware Overseers
"Frank Ch. Eigler" <fche@redhat.com> writes:
> I'd appreciate contact from the dns owner for sourceware.org (ian?) to
> arrange the needed NS changes. We may be able to set up transitional
> records there immediately. The key is adding an NS record that points
> to server2.sourceware.org, which eventually would become the primary.
I am indeed the owner of the sourceware.org domain. Let me know what
you would like me to do.
Note that I think sourceware.org already has an NS record pointing to
server2.sourceware.org.
dig sourceware.org ns
; <<>> DiG 9.11.14-RedHat-9.11.14-2.fc31 <<>> sourceware.org ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 757
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 0ac52b38301bf1596ec194105e38da84ee1aca1a442f20b1 (good)
;; QUESTION SECTION:
;sourceware.org. IN NS
;; ANSWER SECTION:
sourceware.org. 43200 IN NS server1.sourceware.org.
sourceware.org. 43200 IN NS server2.sourceware.org.
sourceware.org. 43200 IN NS server3.sourceware.org.
sourceware.org. 43200 IN NS sourceware.org.
sourceware.org. 43200 IN NS ns2.elastic.org.
;; Query time: 832 msec
;; SERVER: 192.168.42.1#53(192.168.42.1)
;; WHEN: Mon Feb 03 18:44:20 PST 2020
;; MSG SIZE rcvd: 180
Thanks for working on this, and thanks to Red Hat for the hardware.
Ian
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sourceware move
2020-02-04 2:46 ` Ian Lance Taylor
@ 2020-02-04 2:53 ` Frank Ch. Eigler
2020-02-04 20:42 ` Ian Lance Taylor
0 siblings, 1 reply; 4+ messages in thread
From: Frank Ch. Eigler @ 2020-02-04 2:53 UTC (permalink / raw)
To: ian; +Cc: overseers
Hi, Ian -
> I am indeed the owner of the sourceware.org domain. Let me know what
> you would like me to do.
Right:
> Note that I think sourceware.org already has an NS record pointing to
> server2.sourceware.org.
>
> dig sourceware.org ns
Yup, the live zone data has the new machines listed. However, at the
registrar level (org->sourceware.org delegation), the data is older,
and may not work reliably enough after transition:
% dig ns sourceware.org. @a0.org.afilias-nst.info. # any org. nameserver
sourceware.org. 86400 IN NS ns.elastic.org.
sourceware.org. 86400 IN NS sourceware.org.
sourceware.org. 86400 IN NS server1.sourceware.org.
Could you update the nameserver list at the registrar to match
the new set? Thanks!
- FChE
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sourceware move
2020-02-04 2:53 ` Frank Ch. Eigler
@ 2020-02-04 20:42 ` Ian Lance Taylor
0 siblings, 0 replies; 4+ messages in thread
From: Ian Lance Taylor @ 2020-02-04 20:42 UTC (permalink / raw)
To: Frank Ch. Eigler; +Cc: overseers
"Frank Ch. Eigler" <fche@elastic.org> writes:
> Yup, the live zone data has the new machines listed. However, at the
> registrar level (org->sourceware.org delegation), the data is older,
> and may not work reliably enough after transition:
>
> % dig ns sourceware.org. @a0.org.afilias-nst.info. # any org. nameserver
> sourceware.org. 86400 IN NS ns.elastic.org.
> sourceware.org. 86400 IN NS sourceware.org.
> sourceware.org. 86400 IN NS server1.sourceware.org.
>
> Could you update the nameserver list at the registrar to match
> the new set? Thanks!
Done, except that I couldn't change ns.elastic.org to ns2.elastic.org.
I think that in order to do that you'll need to register ns2.elastic.org
with a glue record in the root name servers. Or something like that.
Although I see that ns.elastic.org and ns2.elastic.org have the same IP
address, so it likely doesn't matter.
It may take a little while for the additional name servers to
propagate.
Ian
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-02-04 20:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-03 19:16 sourceware move Frank Ch. Eigler
2020-02-04 2:46 ` Ian Lance Taylor
2020-02-04 2:53 ` Frank Ch. Eigler
2020-02-04 20:42 ` Ian Lance Taylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).