Aus aktuellem Anlass hier ein aus den wegen dummer Software derzeit unerreichbaren "Zugschlus' manchmal nützlichen Antworten" schnell reingepasteter Artikel
Ungenaue Terminologie wird im Internet oft von Leuten verwendet, die
zwar ungefähr wissen, wie die Dinge funktionieren, sich aber nicht im
hinreichenden Maße mit den Hintergründen beschäftigt haben. Dies
erschwert die Kommunikation und ist oft dafür verantwortlich, dass ein
Auftragnehmer nicht das ausführt, was sein Auftraggeber eigentlich
möchte.
Ein besonders von diesem Problem geplagter Bereich der
Internet-Technik ist der Domain Name Service (DNS), da hier in
besonderem Maße die Kommunikation zwischen verschiedenen
Leistungsträgern in unterschiedlichen Unternehmen notwendig ist.
Mit diesem Text will ich versuchen, etwas Klarheit in die Terminologie
zu bringen.
ich sitze im Homeoffice und komme nicht ans Intranet....
Pinging intranet.example.com [62.157.140.133] with 32 bytes of data:
Reply from 62.157.140.133: bytes=32 time=66ms TTL=247
Reply from 62.157.140.133: bytes=32 time=68ms TTL=247
Reply from 62.157.140.133: bytes=32 time=71ms TTL=247
Reply from 62.157.140.133: bytes=32 time=68ms TTL=247
This article was updated, and the issue seems solved. Please look at the last paragraph before adding comments.
Exim has the habit of trying to find out about its host names and IP addresses when it starts up. This has, in the past, been an issue for the Debian packages, since a Debian system might be on a dial-on-demand modem line with expensive costs and thus should not do unnecessary DNS lookup when the MTA is started.
This article tries to describe the issue and which countermeasures debian took, and asks for tips how to solve this in the case of IPv6, where our past measures unfortunately do not directly apply.
I'd like to solicit opinions from people who are more experienced than me with Unix, the local resolver library including /etc/hosts and /etc/nsswitch.conf, DNS, and - especially - the customs that apply on a system running IPv6.
For nearly two years, I have been pondering about a good and failure-resilient DNS setup to implement for my own domains. In the last days, I have set the first prototype into use.
No, I haven't dared to touch zugschlus.de, my most important domain, yet. This is planned for the weekend. So, if you experience difficulties in accessing any of my Internet services, please inform me and allow me to fix the issue.
Today, over the day, access to security.debian.org was intermittent as usual in the last few weeks. But this afternoon, things suddenly got much worse. All my cron-apt installations on and behind firewalls began to yell at me that securiy.debian.org was completely unreachable.
But. Wait. I don't know that IP address. I don't know the host name tartini.debian.org.
Once again, the solution was found in Joey's Blog. Apparently, security.debian.org was moved to the new host, and everything is fine.
Nearly everything.
UPDATE: There has been an Announcement, but not where I would have expected it. The IP address hasn't been mentioned there, though, and that announcement wasn't signed.
UPDATE: There has been one more change to the IP addresses of security.debian.org: It now seems to be round-robin DNS of three hosts. While this is now a real advance compared to the old situation, it has - again - been unannounced to the public. And I get a free trip around my firewalls for the second time in 24 hours. Thanks, guys - I'd surely be twiddling my thumbs otherwise.
