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

1. 11.10.2013, 15:41. min в теме
   «МГТС & GPON»
   ... но крутил wifi как хотел и многое другое навскидку dhcp а за что они должны карать как раз наоборот это...
2. 24.05.2013, 10:37. ic-oksion в теме
   «МЧС РОССИИ. Вакансии»
   ... osi 4 поддержка и обслуживание сервисов microsoft ad dhcp wsus 5 опыт работы с компьютерным оборудованием...
3. 14.11.2012, 12:51. Alex.Skif в теме
   «Системный администратор (Инженер)»
   ... ит-сервисы построены на архитектуре microsoft ad dns dhcp exchange tmg и т п требования 1 знания win-администратора ad dns dhcp exchange tmg и т п 2 знания основы сетей osi и...
4. 29.08.2012, 14:36. d.krysko в теме
   «(Вакансия) Старший Инженер Сетей и телефонии Управления Системной поддержки ДИТ»
   ... windows 2 поддержка работоспособности домена ad dns dhcp файловых хранилищ 3 планирование заказа услуг...
5. 30.07.2012, 19:13. LvovKirill в теме
   «Инженер по оборудованию Cisco»
   ... знания основных сетевых служб и протоколов стека tcp ip dhcp nat ftp icmp spanningtree опыт инсталляции голосовых...
6. 05.04.2012, 15:40. mipinfo в теме
   «Инженер в группу системного администрирования»
   ... policy microsoft sql 2005 2008 exchange 2007 2010 dns dhcp print server дополнительные требования желательно...
7. 27.12.2011, 21:40. naumov.ale в теме
   «Руководитель отдела IT-инфраструктуры»
   ... server 2003 2008 и сетевые службы activedirectory dns dhcp rras remote desktop в условиях распределенной...
8. 09.10.2011, 14:50. .kkursor в теме
   «Помогите настроить bind»
   ... скопировал зону с dns-сервера первого офиса прикрутил dhcp и всё работало до тех пор пока на внешний исторически сложившийся домен не кончилось делегирование т к фирма им владевшая погибла в первом офисе всё осталось по-прежнему связка dns dhcp по каким-то своим причинам не взлетела на шиндошс да но во втором офисе начались проблемы вот конфиг бинда код 14 07 kkursor gw office xxx ru cat etc namedb named conf grep -v refer to the named conf 5 and named 8 man pages and the documentation in usr share doc bind9 for more details if you are going to set up an authoritative server make sure you understand the hairy details of how dns works even with simple mistakes you can break connectivity for affected parties or cause huge amounts of useless internet traffic options relative to the chroot directory if any directory etc namedb pid-file var run named pid dump-file var dump named dump db statistics-file var stats named stats if named is being used only as a local resolver this is a safe default for named to be accessible to the network comment this option specify the proper ip address or delete this option if you have ipv6 enabled on this system uncomment this option for use as a local resolver to give access to the network specify an ipv6 address or the keyword any listen-on-v6 1 these zones are already covered by the empty zones listed below if you remove the related empty zones below comment these 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 make sure you fully understand how dns and bind work there are sometimes non-obvious pitfalls setting up a slave zone is usually simpler nb don t blindly enable the examples below use actual names and addresses instead acl servers key dhcpupdate algorithm hmac-md5 secret key zone ibk local type master allow-update key dhcpupdate servers allow-transfer file dynamic ibk local zone office xxx ru type master file slave office xxx ru zone allow-update key dhcpupdate servers masters forwarders allow-transfer check-names ignore интересующая меня зона office xxx ru она привязана к dhcp с целью получить соответствие выданных адресов доменным именам проблема вот в чём dhcp выдаёт параметры основной шлюз 192 168 10 100...
9. 09.10.2011, 14:04. .kkursor в теме
   «Сказка о потерянном времени»
   ... силу своей кривости но критически важные шлюзы dns-dhcp сервера прокси серверы бэкапов и тд всё под bsd...
10. 24.09.2011, 00:26. Yevgeniya.Voronina в теме
    «помогите разблокировать аккаунт vkontakte»
    ... slip interface физический адрес 00-53-45-00-00-00 dhcp включен нет ip-адрес 178 91 183 251 маска подсети...