Маршруты, прописанные в роутере: 10.0.0.0 255.0.0.0 10.122.238.1 81.211.40.0 255.255.255.0 10.122.238.1 172.16.0.0 255.240.0.0 10.122.238.1 79.98.136.0 255.255.248.0 10.122.238.1 81.211.38.0 255.255.254.0 10.122.238.1 217.78.180.0 255.255.254.0 10.122.238.1 217.78.176.0 255.255.252.0 10.122.238.1 224.0.0.0 255.255.255.0 10.122.238.10 224.0.42.0 255.255.255.0 10.122.238.10 230.3.3.0 255.255.255.0 10.122.238.10 230.3.4.0 255.255.255.0 10.122.238.10 Сейчас, как я писал выше, проблем с DNS больше нет, так что дело было не в маршрутах.

А вот сейчас заработало. Думаю, тему можно закрывать.

f3.vcp.digitalaccess.ru сегодня действительно резолвится. Однако: <1>~$ nslookup ns1.digitalaccess.ru 81.211.38.1 ;; connection timed out; no servers could be reached <1>~$ nslookup f24.vcp.digitalaccess.ru 81.211.38.1 ;; connection timed out; no servers could be reached И с новыми DNS аналогично: <1>~$ nslookup f3.vcp.digitalaccess.ru 217.78.176.1 Server: 217.78.176.1 Address: 217.78.176.1#53 Non-authoritative answer: Name: f3.vcp.digitalaccess.ru Address: 91.233.216.3 <1>~$ nslookup ns1.digitalaccess.ru 217.78.177.250 ;; connection timed out; no servers could be reached <1>~$ nslookup f24.vcp.digitalaccess.ru 217.78.177.250 ;; connection timed out; no servers could be reached <1>~$ nslookup f24.vcp.digitalaccess.ru 217.78.176.1 ;; connection timed out; no servers could be reached

№ договора 1/6253. Не резолвится хост f3.vcp.digitalaccess.ru: <1>~$ ping f3.vcp.digitalaccess.ru ping: unknown host f3.vcp.digitalaccess.ru Если дернуть прописанные в договоре DNS-сервера, видим следующее: <1>~$ nslookup f3.vcp.digitalaccess.ru 81.211.38.1 ;; connection timed out; no servers could be reached <1>~$ nslookup f3.vcp.digitalaccess.ru 81.211.40.2 ;; connection timed out; no servers could be reached dig +trace <1>~$ dig f3.vcp.digitalaccess.ru +trace ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> f3.vcp.digitalaccess.ru +trace ;; global options: +cmd . 139286 IN NS d.root-servers.net. . 139286 IN NS f.root-servers.net. . 139286 IN NS b.root-servers.net. . 139286 IN NS a.root-servers.net. . 139286 IN NS m.root-servers.net. . 139286 IN NS l.root-servers.net. . 139286 IN NS h.root-servers.net. . 139286 IN NS j.root-servers.net. . 139286 IN NS c.root-servers.net. . 139286 IN NS k.root-servers.net. . 139286 IN NS i.root-servers.net. . 139286 IN NS g.root-servers.net. . 139286 IN NS e.root-servers.net. ;; Received 508 bytes from 192.168.0.1#53(192.168.0.1) in 111 ms ru. 172800 IN NS a.dns.ripn.net. ru. 172800 IN NS b.dns.ripn.net. ru. 172800 IN NS d.dns.ripn.net. ru. 172800 IN NS e.dns.ripn.net. ru. 172800 IN NS f.dns.ripn.net. ;; Received 353 bytes from 128.63.2.53#53(128.63.2.53) in 201 ms digitalaccess.ru. 345600 IN NS ns1.digitalaccess.ru. digitalaccess.ru. 345600 IN NS ns2.digitalaccess.ru. dig: couldn't get address for 'ns1.digitalaccess.ru': no more Попробовал dig +trace с другой машины, которая не через Коптево.нет подключена: $ nslookup f3.vcp.digitalaccess.ru Server: 188.120.247.2 Address: 188.120.247.2#53 Non-authoritative answer: Name: f3.vcp.digitalaccess.ru Address: 91.233.216.3 $ dig f3.vcp.digitalaccess.ru +trace ; <<>> DiG 9.7.0-P1 <<>> f3.vcp.digitalaccess.ru +trace ;; global options: +cmd . 3598683 IN NS k.root-servers.net. . 3598683 IN NS m.root-servers.net. . 3598683 IN NS f.root-servers.net. . 3598683 IN NS a.root-servers.net. . 3598683 IN NS j.root-servers.net. . 3598683 IN NS h.root-servers.net. . 3598683 IN NS e.root-servers.net. . 3598683 IN NS c.root-servers.net. . 3598683 IN NS g.root-servers.net. . 3598683 IN NS l.root-servers.net. . 3598683 IN NS d.root-servers.net. . 3598683 IN NS b.root-servers.net. . 3598683 IN NS i.root-servers.net. ;; Received 449 bytes from 188.120.247.2#53(188.120.247.2) in 0 ms ru. 172800 IN NS e.dns.ripn.net. ru. 172800 IN NS a.dns.ripn.net. ru. 172800 IN NS d.dns.ripn.net. ru. 172800 IN NS b.dns.ripn.net. ru. 172800 IN NS f.dns.ripn.net. ;; Received 353 bytes from 192.5.5.241#53(f.root-servers.net) in 4 ms digitalaccess.ru. 345600 IN NS ns2.digitalaccess.ru. digitalaccess.ru. 345600 IN NS ns1.digitalaccess.ru. ;; Received 109 bytes from 193.232.128.6#53(a.dns.ripn.net) in 2 ms f3.vcp.digitalaccess.ru. 86400 IN A 91.233.216.3 digitalaccess.ru. 86400 IN NS ns1.digitalaccess.ru. digitalaccess.ru. 86400 IN NS ns2.digitalaccess.ru. ;; Received 125 bytes from 91.233.216.103#53(ns1.digitalaccess.ru) in 2 ms Возвращаемся к моему компьютеру и видим, что доступ к f3.vcp.digitalaccess.ru и ns1.digitalaccess.ru по IP есть: <1>~$ ping 91.233.216.103 PING 91.233.216.103 (91.233.216.103) 56(84) bytes of data. 64 bytes from 91.233.216.103: icmp_req=1 ttl=61 time=5.33 ms 64 bytes from 91.233.216.103: icmp_req=2 ttl=61 time=7.21 ms ^C --- 91.233.216.103 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 5.338/6.278/7.218/0.940 ms <1>~$ ping 91.233.216.3 PING 91.233.216.3 (91.233.216.3) 56(84) bytes of data. 64 bytes from 91.233.216.3: icmp_req=1 ttl=61 time=5.80 ms 64 bytes from 91.233.216.3: icmp_req=2 ttl=61 time=7.97 ms ^C --- 91.233.216.3 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 5.800/6.887/7.974/1.087 ms <1>~$ nslookup f3.vcp.digitalaccess.ru 91.233.216.103 Server: 91.233.216.103 Address: 91.233.216.103#53 Name: f3.vcp.digitalaccess.ru Address: 91.233.216.3 Но по доменному имени к ним не обратиться, что печально. Роутер есть. Перезагружал - не помогло. Не далее как две недели назад этой проблемы не было. Других проблем с сетью в настоящее время не наблюдаю.