Сообщения со словом
«arpa»

1. 09.10.2011, 14:50. .kkursor в теме
   «Помогите настроить bind»
   ... lines out disable-empty-zone 255 255 255 255 in-addr arpa in addition to the forwarders clause you can force your name server to never initiate queries of its own but always ask its forwarders only by enabling the following line forward only if you ve got a dns server around at your upstream provider enter its ip address here and enable the line below this will make you benefit from its cache thus reduce overall dns traffic in the internet forwarders 195 178 222 2 79 135 229 194 modern versions of bind use a random udp port for each outgoing query by default in order to dramatically reduce the possibility of cache poisoning all users are strongly encouraged to utilize this feature and to configure their firewalls to accommodate it as a last resort in order to get around a restrictive firewall policy you can try enabling the option below use of this option will significantly reduce your ability to withstand cache poisoning attacks and should be avoided if at all possible query-source address port nnnnn first in your etc resolv conf so this server will be queried also make sure to enable it in etc rc conf the traditional root hints mechanism use this or the slave zones below zone type hint file named root slaving the following zones from the root name servers has some significant advantages 1 faster local resolution for your users 2 no spurious traffic will be sent from your network to the roots 3 greater resilience to any potential root server failure ddos on the other hand this method requires more monitoring than the hints file to be sure that an unexpected failure mode has not incapacitated your server name servers that are serving a lot of clients will benefit more from this approach than individual hosts use with caution to use this mechanism uncomment the entries below and comment the hint zone above zone type slave file slave root slave masters 192 5 5 241 f root-servers net notify no zone arpa type slave file slave arpa slave masters 192 5 5 241 f root-servers net notify no zone in-addr arpa type slave file slave in-addr arpa slave masters 192 5 5 241 f root-servers net notify no serving the following zones locally will prevent any queries for these zones leaving your network and going to the root name servers this has two significant advantages 1 faster local resolution for your users 2 no spurious traffic will be sent from your network to the roots rfc 1912 zone localhost type master file master localhost-forward db zone 127 in-addr arpa type master file master localhost-reverse db zone 255 in-addr arpa type master file master empty db rfc 1912-style zone for ipv6 localhost address private use networks rfc 1918 zone 16 172 in-addr arpa type master file master empty db zone 17 172 in-addr arpa type master file master empty db zone 18 172 in-addr arpa type master file master empty db zone 19 172 in-addr arpa type master file master empty db zone 21 172 in-addr arpa type master file master empty db zone 22 172 in-addr arpa type master file master empty db zone 23 172 in-addr arpa type master file master empty db zone 24 172 in-addr arpa type master file master empty db zone 25 172 in-addr arpa type master file master empty db zone 26 172 in-addr arpa type master file master empty db zone 27 172 in-addr arpa type master file master empty db zone 28 172 in-addr arpa type master file master empty db zone 29 172 in-addr arpa type master file master empty db zone 31 172 in-addr arpa type master file master empty db zone 168 192 in-addr arpa type master file master empty db zone 254 169 in-addr arpa type master file master empty db zone 18 198 in-addr arpa type master file master empty db zone 19 198 in-addr arpa type master file master empty db iana reserved old class e space zone 241 in-addr arpa type master file master empty db zone 242 in-addr arpa type master file master empty db zone 243 in-addr arpa type master file master empty db zone 244 in-addr arpa type master file master empty db zone 245 in-addr arpa type master file master empty db zone 246 in-addr arpa type master file master empty db zone 247 in-addr arpa type master file master empty db zone 248 in-addr arpa type master file master empty db zone 249 in-addr arpa type master file master empty db zone 251 in-addr arpa type master file master empty db zone 252 in-addr arpa type master file master empty db zone 253 in-addr arpa type master file master empty db zone 254 in-addr arpa type master file master empty db ipv6 unassigned addresses rfc 4291 zone 1 ip6 arpa type master file master empty db zone 3 ip6 arpa type master file master empty db zone 4 ip6 arpa type master file master empty db zone 5 ip6 arpa type master file master empty db zone 6 ip6 arpa type master file master empty db zone 7 ip6 arpa type master file master empty db zone 8 ip6 arpa type master file master empty db zone 9 ip6 arpa type master file master empty db zone a ip6 arpa type master file master empty db zone b ip6 arpa type master file master empty db zone c ip6 arpa type master file master empty db zone d ip6 arpa type master file master empty db zone e ip6 arpa type master file master empty db zone 1 f ip6 arpa type master file master empty db zone 2 f ip6 arpa type master file master empty db zone 3 f ip6 arpa type master file master empty db zone 4 f ip6 arpa type master file master empty db zone 5 f ip6 arpa type master file master empty db zone 6 f ip6 arpa type master file master empty db zone 7 f ip6 arpa type master file master empty db zone 8 f ip6 arpa type master file master empty db zone 9 f ip6 arpa type master file master empty db zone a f ip6 arpa type master file master empty db zone b f ip6 arpa type master file master empty db zone 1 e f ip6 arpa type master file master empty db zone 2 e f ip6 arpa type master file master empty db zone 3 e f ip6 arpa type master file master empty db zone 4 e f ip6 arpa type master file master empty db zone 5 e f ip6 arpa type master file master empty db zone 6 e f ip6 arpa type master file master empty db zone 7 e f ip6 arpa type master file master empty db ipv6 ula rfc 4193 zone c f ip6 arpa type master file master empty db zone d f ip6 arpa type master file master empty db ipv6 link local rfc 4291 zone 8 e f ip6 arpa type master file master empty db zone 9 e f ip6 arpa type master file master empty db zone a e f ip6 arpa type master file master empty db zone b e f ip6 arpa type master file master empty db ipv6 deprecated site-local addresses rfc 3879 zone c e f ip6 arpa type master file master empty db zone d e f ip6 arpa type master file master empty db zone e e f ip6 arpa type master file master empty db zone f e f ip6 arpa type master file master empty db ip6 int is deprecated rfc 4159 zone ip6 int type master file master empty db nb do not use the ip addresses below they are faked and only serve demonstration documentation purposes example slave zone config entries it can be convenient to become a slave at least for the zone your own domain is in ask your network administrator for the ip address of the responsible master name server do not forget to include the reverse lookup zone this is named after the first bytes of the ip address in reverse order with in-addr arpa appended or ip6 arpa for ipv6 before starting to set up a master zone...
2. 11.11.2010, 01:06. Chameleon в теме
   «Maxima на Corum'е»
   ... macsyma included the advanced research projects agency arpa department of defense the us department of energy and other government and private sources the original idea first voiced by marvin minsky was to automate the kinds of manipulations done by mathematicians as a step toward understanding the power of computers to exhibit a kind of intelligent behavior the undertaking grew out of a previous effort at mitre corp called mathlab work of carl engelman and others plus the mit thesis work of joel moses on symbolic integration and the mit thesis work of william a martin the new effort was dubbed macsyma project mac s symbolic manipulator the original core design was done in july 1968 and coding began in july 1969 this was long before the days of personal computers and cheap memory initial development was centered around a single computer shared with the artificial intelligence laboratory a dec pdp-6 this was replaced by newer more powerful machines over the years and eventually the mathlab group acquired its own dec-pdp-10 mit-ml running the its operating system this machine became a host on the early arpanet predecessor to the internet which helped it gain a wider audience as the effort grew in scope and ability the general interest it created led to attempts to port the code that is to take the series of instructions which had been written for one machine and operating system and adapt them to run on another different system the earliest such effort was the running of macsyma in a maclisp environment on a ge honeywell multics mainframe another system at mit the multics environment provided essentially unlimited address space but for various reasons the system was not favored by programmers and the multics implementation was never popular the next effort came about when a group at mit designed and implemented a machine which was based on the notion that hardware support of lisp would make it possible to overcome problems that inhibited the solution of many interesting problems the lisp machine clearly had to support macsyma the largest lisp program of the day and the effort paid off with probably the best environment for macsyma to date although requiring something of an expert perspective lisp machines as well as other special purpose hardware tended to become slow and expensive compared to off-the-shelf machines built around merchant-semiconductor cpus and so the two companies that were spun off from mit symbolics inc and lmi both eventually disappeared texas instruments built a machine called the explorer bases on the lmi design but also stopped production around 1980 the idea of porting macsyma began to be more interesting and the unix based vaxima distribution which ran on a lisp system built at the university of california at berkeley for vax unix demonstrated that it was both possible and practical to run the software on less expensive systems this system franz lisp was implemented primarily in lisp with some parts written in c once the code stabilized the new version opened up porting possibilities ultimately producing at least six variations on the theme which included macsyma maxima paramax paramacs punimax aljbar and vaxima these have followed somewhat different paths and most were destined to fade into the sunset the two which survived obscurity maxima and macsyma we will discuss below punimax was actually an offshoot of maxima some time around 1994 bruno haible author of clisp ported maxima to clisp due to the legal concerns of richard petti then the owner of the commercial macsyma the name was changed to punimax it has not seen much activity since the initial port and although it is still available the ability of the main maxima distribution to compile on clisp makes further development of punimax unlikely there is a certain surprising aspect in this multiplicity of versions and platforms given how the code seemed tied to the development environment which included a unique operating system fortunately berkeley s building a replica of the maclisp environment on the mit-ml pdp-10 using tools available in almost any unix c environment helped solve this problem complicating the matter was the eventual demise of the pdp-10 and maclisp systems as common lisp resembling lisp-machine lisp influenced by bbn lisp and researchers at stanford carnegie mellon university and xerox began to take hold it seemed sensible to re-target the code to make it compatible with what eventually became the ansi common lisp standard since almost everything needed for for macsyma can be done in ansi cl the trend toward standardization made many things simpler there are a few places where the language is not standardized in particular connecting to modules written in other languages but much of the power of the system can be expressed within ansi cl it is a trend the maxima project is planning to carry on to maintain and expand on this flexibility which has emerged with all these versions in recent history there are two which have been major players due this time more to economics than to code quality 1982 was a watershed year in many respects for macsyma it marks clearly the branching of macsyma into two distinct products and ultimately gave rise to the events which have made maxima both possible and desirable mit had decided with the gradual spread of computers throughout the academic world to put macsyma on the market commercially using as a marketing partner the firm of arthur d little inc this version was sold to the symbolics inc which depending on your perspective either turned the project into a significant marketing effort to help sell their high-priced lisp machines or was a diversionary tactic to deny their competitors lmi this program at the same time mit forced uc berkeley richard fateman to withdraw the copies from about 50 sites of the vax unix and vax vms versions of macsyma that he had distributed with mit s consent until some agreement could be reached for technology transfer symbolics hired some of the mit staff to work at symbolics in order to improve the code which was now proprietary the mit-ml pdp-10 also went off the arpanet in 1983 interestingly the closing of the mit...
3. 31.08.2009, 11:56. .kkursor в теме
   «Отсылка писем с форума»
   ... 53 non-authoritative answer 76 227 177 195 in-addr arpa name corum mephist ru authoritative answers can be found from 227 177 195 in-addr arpa nameserver ns5 adb ru 227 177 195 in-addr arpa nameserver ns adb ru ns adb ru internet address...
4. 30.06.2009, 13:53. .kkursor в теме
   «Заблокировался Вконтакте»
   ... 53 non-authoritative answer 26 191 169 95 in-addr arpa name ns2 km35408 keymachine de authoritative answers can be found from 191 169 95 in-addr arpa nameserver ns keyweb de 191 169 95 in-addr arpa nameserver ns2 keyweb de ns keyweb de internet...