DNS Propagation Success Block for React

Nothing was looked up. The record, the eight resolvers and their addresses (a documentation range) are typed sample data, and Check again follows a typed sequence of 3, 5, 7 and 8 resolvers answering, after a short wait. To wire it, replace the wait in check with a query to each resolver (or to your own probes), build each resolver's state from its answer, and say in the sentence what the pending ones still return.

Because a resolver keeps an answer until its copy expires, which is the TTL the old record had. The page says so: the old record's TTL was 600 seconds, so the pending resolvers drop it within 10 minutes. The 10 is worked out from the typed old TTL, and the pending count is worked out from the sequence.

It waits a moment (the button stays focusable and says "Checking…", so it never changes size), moves the next two pending resolvers to Live, updates the bar, the count and the sentence, and says what changed in a polite status message. At 8 of 8 the sentence says the record has propagated, the button reads "All checked" and pressing it says nothing remains to check.

Yes. Each resolver says Live or Pending in words, with a filled dot for Live and a hollow one for Pending, and the line under its address says what it answers ("answers 203.0.113.42" or "still answers 192.0.2.17"). The bar is a drawing hidden from assistive technology, since "3 of 8" says the same.

The record as a zone-file line (shop 300 IN A 203.0.113.42), through the browser's clipboard. A screen reader hears that it was copied, and the record cells are left-to-right whatever the page's direction.

The header's button drops under the sentence, the four record cells become two rows of two, the resolvers are one column, and Check again is full width at the foot.

It is a Shine Button used as a link to your own route. It is a Shine Button with render set to an a element and nativeButton={false}.