<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>recursion requested but not available &#8211; SMsoft &#8211; informatica e dintorni</title>
	<atom:link href="https://blog.smsoft.it/tag/recursion-requested-but-not-available/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.smsoft.it</link>
	<description>consigli settimanali su MacOS, GNU/Linux ed Open Source</description>
	<lastBuildDate>Tue, 16 Mar 2021 12:44:26 +0000</lastBuildDate>
	<language>it-IT</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=93032</generator>
	<item>
		<title>dig mostra il messaggio &#8220;recursion requested but not available&#8221;</title>
		<link>https://blog.smsoft.it/2021/03/16/dig-mostra-il-messaggio-recursion-requested-but-not-available/</link>
					<comments>https://blog.smsoft.it/2021/03/16/dig-mostra-il-messaggio-recursion-requested-but-not-available/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 16 Mar 2021 09:30:00 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[+nocookie]]></category>
		<category><![CDATA[BIG-IP]]></category>
		<category><![CDATA[dig]]></category>
		<category><![CDATA[recursion requested but not available]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=4901</guid>

					<description><![CDATA[Dopo aver aggiornato una Debian 9 a Debian 10 Buster ho riscontrato uno strano comportamento di dig. Praticamente qualsiasi interrogazione mi tornava sempre l&#8217;avviso &#8220;WARNING: recursion requested but not available&#8221;, ad esempio: $ dig google.com ; &#60;&#60;>> DiG 9.11.5-P4-5.1+deb10u3-Debian &#60;&#60;>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER&#60;&#60;- opcode: QUERY, status: FORMERR, id: ... <a title="dig mostra il messaggio &#8220;recursion requested but not available&#8221;" class="read-more" href="https://blog.smsoft.it/2021/03/16/dig-mostra-il-messaggio-recursion-requested-but-not-available/" aria-label="Per saperne di più su dig mostra il messaggio &#8220;recursion requested but not available&#8221;">Leggi tutto</a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Dopo aver aggiornato una Debian 9 a Debian 10 Buster ho riscontrato uno strano comportamento di dig. Praticamente qualsiasi interrogazione mi tornava sempre l&#8217;avviso &#8220;WARNING: recursion requested but not available&#8221;, ad esempio:</p>



<pre class="wp-block-preformatted">$ dig google.com
; &lt;&lt;>> DiG 9.11.5-P4-5.1+deb10u3-Debian &lt;&lt;>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER&lt;&lt;- opcode: QUERY, status: FORMERR, id: 33479
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 944e89afaed116f4 (echoed)
;; QUESTION SECTION:
;google.com. IN A

;; Query time: 0 msec
;; SERVER: 10.10.70.100#53(10.109.70.100)
;; WHEN: mar mar 16 13:10:22 CET 2021
;; MSG SIZE rcvd: 51</pre>



<p class="wp-block-paragraph">Questo accade perché in <strong>BIG-IP 14.1.0</strong> è stato implementato un sistema di controllo tramite cookie definito in <a href="https://tools.ietf.org/html/rfc7873" target="_blank" rel="noopener">Internet Engineering Task Force RFC 7873</a> e la nuova versione di DIG invia il DNS cookie di default.</p>



<p class="wp-block-paragraph">Va quindi disabilitato l&#8217;invio del cookie, manualmente usando l&#8217;opzione es:</p>



<pre id="block-8ead3c6b-eb88-4898-aa64-a0ccd844bd7e" class="wp-block-preformatted">$ dig +nocookie google.com</pre>



<p class="wp-block-paragraph">oppure automaticamente creando il file <strong>~/.digrc</strong> ed inserendo li la direttiva:</p>



<pre class="wp-block-preformatted">+nocookie</pre>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2021/03/16/dig-mostra-il-messaggio-recursion-requested-but-not-available/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
