Your message dated Sat, 03 Oct 2026 17:33:50 +0100
with message-id 
<646c96661b8f99ff640a4db71fada735eac883d8.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1109442: 'Temporary failure in name resolution' in 
debian master mirror trace (ftp.kr.d.o)
has caused the Debian Bug report #1109442,
regarding 'Temporary failure in name resolution' in debian master mirror trace 
(ftp.kr.d.o)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1109442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109442
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mirrors
Severity: bug

User: [email protected]
Usertags: mirror-list

Hello, this is ftp.kaist.ac.kr (known as ftp.kr.debian.org) manager, Roul.

Our mirror report in master server says 'Temporary failure in name resolution'
https://mirror-master.debian.org/status/mirror-info/ftp.kaist.ac.kr.html

This issue needs to be investigated.

Thank you.

Regards,

Roul

--- End Message ---
--- Begin Message ---
On Fri, 2025-07-18 at 07:15 +0100, Adam D. Barratt wrote:
> Hi,
> 
> On Fri, 2025-07-18 at 10:00 +0900, 신도윤 wrote:
> > Our mirror report in master server says 'Temporary failure in name
> > resolution'
> > https://mirror-master.debian.org/status/mirror-info/ftp.kaist.ac.kr.html
> > 
> > This issue needs to be investigated.
> 
> I'm failing to resolve the domain from various other locations.
[...]
> In addition to the DNS issue, if you look slightly further back in
> your status page, you'll notice that the mirror has been reported as
> increasingly out of sync, and was approximately 2.5 days behind the
> last time we were able to successfully contact it (2025-07-17
> 13:45:52 UTC).

It looks like the DNS issues have been resolved in the meantime, so I'm
closing this bug.

There does appear to have been a recent sync issue, but things look
better since yesterday, so I assume you are aware / have resolved it.

Regards,

Adam

--- End Message ---

Reply via email to