[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Problem reaching anongit.kde.org
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2019-01-03 18:55:29
Message-ID: 515514769.VmWe7HtVzF () xps
[Download RAW message or body]

El dijous, 3 de gener de 2019, a les 16:26:16 CET, Freek de Kruijf va escriure:
> Op donderdag 3 januari 2019 15:15:28 CET schreef Andrius Å tikonas:
> > On Thu, Jan 03, 2019 at 03:04:53PM +0100, Freek de Kruijf wrote:
> > > When trying to use scripts/update_xml to update some documentation in
> > > docmessages I get an error like:
> > > fatal: unable to look up anongit.kde.org (port 9418) (Temporary failure in
> > > name resolution)
> > > 
> > > Is this a known problem or has there been an announcement about
> > > maintenance?
> > Yes, it is a known problem which was already fixed but DNS propagation takes
> > a while.
> > 
> > Andrius
> 
> There may be another problem.
> If I just do, which goes to the DNS server in my modem:
> dig git.anonscm.local-kde.org.
> I get SERVFAIL.
> The modem has some DNS servers configured, which should resolve the request:
> dig @194.109.6.66 git.anonscm.local-kde.org.
> Again SERVFAIL.
> If I do the request at the authoritative DNS of kde.org, like:
> dig @a.ns.bytemark.co.uk. git.anonscm.local-kde.org.
> I get: connection timed out; no servers could be reached
> However a.ns.bytemark.co.uk is not the authoritative DNS for anonscm.local-
> kde.org, which seems to be ns1.kde.org, according to the SOA record.
> So I tried:
> dig @ns1.kde.org. anonscm.local-kde.org. ns
> which showed no NS record, but
> dig @ns1.kde.org. local-kde.org. ns
> did.
> So finally:
> dig @ns1.kde.org. git.anonscm.local-kde.org.
> showed: 31.216.41.69, lifetime 60 seconds
> However a request to google-public-dns-a.google.com (8.8.8.8) showed:
> dig @8.8.8.8 git.anonscm.local-kde.org.
> showed: 138.197.213.241, lifetime 59 seconds
> 
> So, what is going on??????

I suggest you ask the sysadmins if you think there's something wrong with the DNS setup or servers

Cheers,
  Albert

> 
> 




[prev in list] [next in list] [prev in thread] [next in thread]