<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dns on C&amp;CZ News</title>
    <link>https://cncz.science.ru.nl/tags/dns/</link>
    <description>Recent content in Dns on C&amp;CZ News</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>postmaster</managingEditor>
    <lastBuildDate>Sun, 21 Feb 2021 07:10:00 +0100</lastBuildDate><atom:link href="https://cncz.science.ru.nl/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DNS problems from outside with ru.nl</title>
      <link>https://cncz.science.ru.nl/cpk/1276/</link>
      <pubDate>Sun, 21 Feb 2021 07:10:00 +0100</pubDate>
      <author></author>
      <guid>https://cncz.science.ru.nl/cpk/1276/</guid>
      <description>&lt;p&gt;The central DNS servers for ru.nl for external requests had problems,
because they received too many requests, which resulted in science.ru.nl
and others not being found. DNS names within ru.nl then will not resolve
to an IP address. We enlarged some TTLs (Time-To+lives) to try to lessen
the problem. These small TTLs were meant to be able to move a service to
a new server in case of problems, but now they just make the problem
bigger. After starting VPN you won&amp;rsquo;t notice this problem, because the
internal DNS servers that you use then are not affected. Changes to the
RU DNS servers hopefully lessened or removed the problems as of
2021-02-23 14:30.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DNS broken for subdomains of ru.nl</title>
      <link>https://cncz.science.ru.nl/cpk/1275/</link>
      <pubDate>Thu, 11 Feb 2021 00:00:00 +0100</pubDate>
      <author></author>
      <guid>https://cncz.science.ru.nl/cpk/1275/</guid>
      <description>&lt;p&gt;DNS-servers for ru.nl did not serve information about subdomains such as
science.ru.nl. Thus no DNS-name will resolve to an IP address at FNWI. A
workaround is to use as DNS servers: 131.174.224.4 en 8.8.8.8. If you
try to connect to a service for the first time after ca 11:15, you&amp;rsquo;ll
get an error like: &amp;ldquo;No such domain&amp;rdquo; or &amp;ldquo;Cannot resolve&amp;rdquo;. Restarting RU
DNS servers at 12:45 may have fixed the problem. Without a real
explanation, the problem went away after a few hours.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
