Janus TCP/IP Base V7.8 changes - Revision history

Admin: Content removed to M204int page of same name

2013-10-17T21:50:49Z

Content removed to M204int page of same name

← Older revision		Revision as of 21:50, 17 October 2013
Line 1:		Line 1:
	~~The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.~~		Content moved to M204int page of same name, but history preserved here.

	~~==DNS Retries==~~
	~~Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,~~
	~~the <var>[[JANUS NAMESERVER]]</var> command had no facility to call for a retry of~~
	~~a DNS UDP packet for which no response is received.~~
	~~This meant that if <var class="product">Janus</var> does a DNS lookup just when the target nameserver~~
	~~is down for an instant, or if the UDP packet gets lost on the network (IP~~
	~~networks don't have to guarantee delivery of IP packets), the DNS lookup~~
	~~could fail.~~

	~~The version 7.8 "DNS Retries" feature is~~
	~~a <var>RETRIES</var> parameter for the <var>JANUS NAMESERVER</var> command.~~
	~~Setting <var>RETRIES</var> to a positive integer value, say 2, instructs <var class="product">Janus</var>~~
	~~to retry as many as two times if no response was received to a DNS lookup.~~
	~~Setting <var>RETRIES</var> to 0, its default, means no retries are attempted.~~

	~~On a swamped network, it is probably better to~~
	~~set a <var>JANUS NAMESERVER TIMEOUT</var> value of, say, 3 and a <var>RETRIES</var> setting of 2, rather than to set <var>TIMEOUT</var> to 10 with <var>RETRIES</var> at 0. This is so because:~~
	*If a packet gets dropped, there is no benefit to ~~waiting 10 seconds instead~~ of 3.
	*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).

	~~It probably does not make sense to set <var>RETRIES</var>~~
	~~to a value greater than 2: if packets are being dropped so frequently~~
	~~that three consecutive DNS requests are dropped~~, ~~you have problems much more serious than the failed lookups.~~


	~~{{Template:Content index: V7~~.~~8 Release Notes}}~~

JALWiccan: 1 revision

2012-06-19T22:07:56Z

1 revision

← Older revision	Revision as of 22:07, 19 June 2012
(No difference)

JAL2 at 22:07, 19 June 2012

2012-06-19T22:07:45Z

← Older revision		Revision as of 22:07, 19 June 2012
Line 5:		Line 5:
	the <var>[[JANUS NAMESERVER]]</var> command had no facility to call for a retry of		the <var>[[JANUS NAMESERVER]]</var> command had no facility to call for a retry of
	a DNS UDP packet for which no response is received.		a DNS UDP packet for which no response is received.
	This meant that if <var class="product>Janus</var> does a DNS lookup just when the target nameserver		This meant that if <var class="product">Janus</var> does a DNS lookup just when the target nameserver
	is down for an instant, or if the UDP packet gets lost on the network (IP		is down for an instant, or if the UDP packet gets lost on the network (IP
	networks don't have to guarantee delivery of IP packets), the DNS lookup		networks don't have to guarantee delivery of IP packets), the DNS lookup
Line 12:		Line 12:
	The version 7.8 "DNS Retries" feature is		The version 7.8 "DNS Retries" feature is
	a <var>RETRIES</var> parameter for the <var>JANUS NAMESERVER</var> command.		a <var>RETRIES</var> parameter for the <var>JANUS NAMESERVER</var> command.
	Setting <var>RETRIES</var> to a positive integer value, say 2, instructs <var class="product>Janus</var>		Setting <var>RETRIES</var> to a positive integer value, say 2, instructs <var class="product">Janus</var>
	to retry as many as two times if no response was received to a DNS lookup.		to retry as many as two times if no response was received to a DNS lookup.
	Setting <var>RETRIES</var> to 0, its default, means no retries are attempted.		Setting <var>RETRIES</var> to 0, its default, means no retries are attempted.

JAL2 at 14:30, 19 June 2012

2012-06-19T14:30:00Z

JAL2 at 19:15, 16 May 2011

2011-05-16T19:15:11Z

← Older revision		Revision as of 19:15, 16 May 2011
Line 1:		Line 1:
	~~{{Hierarchy header}}~~
	The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.		The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.

Line 27:		Line 27:
	that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.		that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.

	{{~~Hierarchy footer~~}}
			{{Template:Content index: V7.8 Release Notes}}

JAL at 20:43, 11 March 2011

2011-03-11T20:43:06Z

JAL: /* DNS Retries */

2011-03-02T01:20:22Z

DNS Retries

← Older revision		Revision as of 01:20, 2 March 2011
Line 3:		Line 3:

	==DNS Retries==		==DNS Retries==
	Prior to ~~Sirmods~~ Version 7.8,		Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,
	the [[JANUS NAMESERVER]] command had no facility to call for a retry of		the [[JANUS NAMESERVER]] command had no facility to call for a retry of
	a DNS UDP packet for which no response is received.		a DNS UDP packet for which no response is received.

JAL at 04:43, 10 December 2010

2010-12-10T04:43:12Z

← Older revision		Revision as of 04:43, 10 December 2010
Line 4:		Line 4:
	==DNS Retries==		==DNS Retries==
	Prior to Sirmods Version 7.8,		Prior to Sirmods Version 7.8,
	the JANUS NAMESERVER command had no facility to call for a retry of		the [[JANUS NAMESERVER]] command had no facility to call for a retry of
	a DNS UDP packet for which no response is received.		a DNS UDP packet for which no response is received.
	This meant that if Janus does a DNS lookup just when the target nameserver		This meant that if Janus does a DNS lookup just when the target nameserver
Line 13:		Line 13:
	The version 7.8 DNS Retries feature is		The version 7.8 DNS Retries feature is
	a RETRIES parameter for the JANUS NAMESERVER command.		a RETRIES parameter for the JANUS NAMESERVER command.
			Setting RETRIES to a positive integer value, say 2, instructs Janus
			to retry as many as two times if no response was received to a DNS lookup.
			Setting RETRIES to 0, its default, means no retries are attempted.

			On a swamped network, it is probably better to
			set a JANUS NAMESERVER TIMEOUT value of, say, 3 and a RETRIES setting of 2, rather than to set TIMEOUT to
			10 with RETRIES 0. This is so because:
			*If a packet gets dropped, there is no benefit to waiting 10 seconds instead of 3.
			*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).

			It probably does not make sense to set RETRIES
			to a value greater than 2: if packets are being dropped so frequently
			that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.

	{{Hierarchy footer}}		{{Hierarchy footer}}

JAL at 04:16, 10 December 2010

2010-12-10T04:16:50Z

@@ Line 1: / Line 1: @@
 {{Hierarchy header}}
 The following features are new or changed in [[Janus TCP/IP Base]].
 {{Hierarchy footer}}

JAL: Created page with "{{Hierarchy header}} The following features are new or changed in Janus TCP/IP Base. {{Hierarchy footer}}"

2010-12-10T04:11:36Z

Created page with "{{Hierarchy header}} The following features are new or changed in Janus TCP/IP Base. {{Hierarchy footer}}"

New page

{{Hierarchy header}}
The following features are new or changed in [[Janus TCP/IP Base]].

{{Hierarchy footer}}

← Older revision		Revision as of 14:30, 19 June 2012
Line 1:		Line 1:

	The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.		The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.

	==DNS Retries==		==DNS Retries==
	Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,		Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,
	the [[JANUS NAMESERVER]] command had no facility to call for a retry of		the <var>[[JANUS NAMESERVER]]</var> command had no facility to call for a retry of
	a DNS UDP packet for which no response is received.		a DNS UDP packet for which no response is received.
	This meant that if <var class="product>Janus</var> does a DNS lookup just when the target nameserver		This meant that if <var class="product>Janus</var> does a DNS lookup just when the target nameserver
Line 12:		Line 11:

	The version 7.8 "DNS Retries" feature is		The version 7.8 "DNS Retries" feature is
	a RETRIES parameter for the JANUS NAMESERVER command.		a <var>RETRIES</var> parameter for the <var>JANUS NAMESERVER</var> command.
	Setting RETRIES to a positive integer value, say 2, instructs <var class="product>Janus</var>		Setting <var>RETRIES</var> to a positive integer value, say 2, instructs <var class="product>Janus</var>
	to retry as many as two times if no response was received to a DNS lookup.		to retry as many as two times if no response was received to a DNS lookup.
	Setting RETRIES to 0, its default, means no retries are attempted.		Setting <var>RETRIES</var> to 0, its default, means no retries are attempted.

	On a swamped network, it is probably better to		On a swamped network, it is probably better to
	set a JANUS NAMESERVER TIMEOUT value of, say, 3 and a RETRIES setting of 2, rather than to set TIMEOUT to		set a <var>JANUS NAMESERVER TIMEOUT</var> value of, say, 3 and a <var>RETRIES</var> setting of 2, rather than to set <var>TIMEOUT</var> to 10 with <var>RETRIES</var> at 0. This is so because:
	10 with RETRIES 0. This is so because:
	*If a packet gets dropped, there is no benefit to waiting 10 seconds instead of 3.		*If a packet gets dropped, there is no benefit to waiting 10 seconds instead of 3.
	*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).		*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).

	It probably does not make sense to set RETRIES		It probably does not make sense to set <var>RETRIES</var>
	to a value greater than 2: if packets are being dropped so frequently		to a value greater than 2: if packets are being dropped so frequently
	that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.		that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.

← Older revision		Revision as of 20:43, 11 March 2011
Line 1:		Line 1:
	{{Hierarchy header}}		{{Hierarchy header}}
	The following features are new or changed in [[Janus TCP/IP Base]].		The following features are new or changed in <var class="product">[[Janus TCP/IP Base]]</var>.

	==DNS Retries==		==DNS Retries==
	Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,		Prior to <var class="product">[[Sirius Mods]]</var> Version 7.8,
	the [[JANUS NAMESERVER]] command had no facility to call for a retry of		the [[JANUS NAMESERVER]] command had no facility to call for a retry of
	a DNS UDP packet for which no response is received.		a DNS UDP packet for which no response is received.
	This meant that if Janus does a DNS lookup just when the target nameserver		This meant that if <var class="product>Janus</var> does a DNS lookup just when the target nameserver
	is down for an instant, or if the UDP packet gets lost on the network (IP		is down for an instant, or if the UDP packet gets lost on the network (IP
	networks don't have to guarantee delivery of IP packets), the DNS lookup		networks don't have to guarantee delivery of IP packets), the DNS lookup
	could fail.		could fail.

	The version 7.8 DNS Retries feature is		The version 7.8 "DNS Retries" feature is
	a RETRIES parameter for the JANUS NAMESERVER command.		a RETRIES parameter for the JANUS NAMESERVER command.
	Setting RETRIES to a positive integer value, say 2, instructs Janus		Setting RETRIES to a positive integer value, say 2, instructs <var class="product>Janus</var>
	to retry as many as two times if no response was received to a DNS lookup.		to retry as many as two times if no response was received to a DNS lookup.
	Setting RETRIES to 0, its default, means no retries are attempted.		Setting RETRIES to 0, its default, means no retries are attempted.

	On a swamped network, it is probably better to		On a swamped network, it is probably better to
	set a JANUS NAMESERVER TIMEOUT value of, say, 3 and a RETRIES setting of 2, rather than to set TIMEOUT to		set a JANUS NAMESERVER TIMEOUT value of, say, 3 and a RETRIES setting of 2, rather than to set TIMEOUT to
	10 with RETRIES 0. This is so because:		10 with RETRIES 0. This is so because:
	*If a packet gets dropped, there is no benefit to waiting 10 seconds instead of 3.		*If a packet gets dropped, there is no benefit to waiting 10 seconds instead of 3.
	*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).		*It is very unlikely that it would take a nameserver 3 seconds to respond to a received request (including packet turnaround time).

	It probably does not make sense to set RETRIES		It probably does not make sense to set RETRIES
	to a value greater than 2: if packets are being dropped so frequently		to a value greater than 2: if packets are being dropped so frequently
	that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.		that three consecutive DNS requests are dropped, you have problems much more serious than the failed lookups.

	{{Hierarchy footer}}		{{Hierarchy footer}}