Janus TCP/IP Base V7.8 changes: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{Hierarchy header}} The following features are new or changed in Janus TCP/IP Base. {{Hierarchy footer}}") |
mNo edit summary |
||
| 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 [[Janus TCP/IP Base]]. | ||
==DNS Retries== | |||
Prior to Sirmods Version 7.8, | |||
the JANUS NAMESERVER command had no facility to call for a retry of | |||
a DNS UDP packet for which no response is received. | |||
This meant that if Janus 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 RETRIES parameter for the JANUS NAMESERVER command. | |||
{{Hierarchy footer}} | {{Hierarchy footer}} | ||
Revision as of 04:16, 10 December 2010
{{#hierarchy-top:}} The following features are new or changed in Janus TCP/IP Base.
DNS Retries
Prior to Sirmods Version 7.8, the JANUS NAMESERVER command had no facility to call for a retry of a DNS UDP packet for which no response is received. This meant that if Janus 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 RETRIES parameter for the JANUS NAMESERVER command.
{{#hierarchy-bottom:}}