что-то мне подсказывает, что проблема не с ДНС, а с раутингом...
Code:
....
Jan 1 03:00:07 udhcpc[100]: udhcpc (v0.9.9-pre) started
Jan 1 03:00:07 dhcp client: deconfig: lease is lost
Jan 1 03:00:09 udhcpc[100]: Lease of 10.19.16.16 obtained, lease time 86400
Jan 1 03:00:10 dnsmasq[76]: read /etc/hosts - 5 addresses
Jan 1 03:00:10 dnsmasq[76]: reading /tmp/resolv.conf
Jan 1 03:00:10 dnsmasq[76]: using nameserver 217.170.80.83#53
Jan 1 03:00:10 dnsmasq[76]: using nameserver 81.9.4.2#53
Jan 1 03:00:10 dhcp client: bound IP : 10.19.16.16 from 10.19.16.1
Jan 1 03:00:10 pppd[110]: Plugin rp-pppoe.so loaded.
Jan 1 03:00:10 pppd[110]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
Jan 1 03:00:10 pppd[112]: pppd 2.4.2 started by admin, uid 0
Jan 1 03:00:10 pppd[112]: Using interface ppp0
Jan 1 03:00:10 pppd[112]: local IP address 10.64.64.64
Jan 1 03:00:10 pppd[112]: remote IP address 10.112.112.112
Jan 1 03:00:13 kernel: printer.c: usblp0 Device ID string [69/max 1552]='MFG:Xerox;CMD:GDI;MDL:Phaser 3117;CLS:PRINTER;MODE:GDI;STATUS:IDLE;'
Jan 1 03:00:13 kernel: printer.c: Parsing USBLPID...
Jan 1 03:00:22 kernel: kjournald starting. Commit interval 5 seconds
Jan 1 03:00:22 kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jan 1 03:00:22 kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
Jan 1 03:00:22 kernel: EXT3-fs: recovery complete.
Jan 1 03:00:22 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 1 03:00:22 USB storage: ext3 fs at /dev/discs/disc0/part1 mounted to /tmp/mnt/disc0_1
Jan 1 03:00:22 kernel: MSDOS FS: IO charset utf8
Jan 1 03:00:22 kernel: MSDOS FS: Using codepage 866
Jan 1 03:00:22 USB storage: vfat fs at /dev/discs/disc0/part3 mounted to /tmp/mnt/disc0_3
Jan 1 03:00:23 kernel: Adding Swap: 1020116k swap-space (priority -1)
Jan 1 03:00:23 System log daemon exiting.
Jan 1 03:00:23 syslogd started: BusyBox v1.1.3
Jan 1 03:00:24 /opt/sbin/cron[195]: (CRON) STARTUP (V5.0)
Jan 1 03:00:24 xinetd[201]: xinetd Version 2.3.14 started with no options compiled in.
Jan 1 03:00:24 xinetd[201]: Started working: 1 available service
Jan 1 03:00:25 dropbear[221]: Running in background
Jan 1 03:01:08 pppoe-relay[95]: PADO packet from 00:90:1a:41:f1:8e on interface vlan1 does not have Relay-Session-Id tag
Jan 1 03:01:08 pppoe-relay[95]: PADO packet from 00:90:1a:41:da:0d on interface vlan1 does not have Relay-Session-Id tag
Jan 1 03:01:08 pppoe-relay[95]: PADO packet from 00:17:df:f3:90:1a on interface vlan1 does not have Relay-Session-Id tag
Jan 1 03:01:08 pppd[112]: PPP session is 4916
Jan 1 03:01:08 pppd[112]: Connect: ppp0 <--> vlan1
Jan 1 03:01:08 pppoe-relay[95]: PADS packet from 00:90:1a:41:f1:8e on interface vlan1 does not have Relay-Session-Id tag
Jan 1 03:01:09 pppd[112]: CHAP authentication succeeded
Jan 1 03:01:09 pppd[112]: peer from calling number 00:90:1A:41:F1:8E authorized
Jan 1 03:01:09 pppd[112]: Local IP address changed to 89.112.6.106
Jan 1 03:01:09 pppd[112]: Remote IP address changed to 81.9.101.117
Jan 1 03:01:09 dnsmasq[76]: reading /tmp/resolv.conf
Jan 1 03:01:09 dnsmasq[76]: using nameserver 81.222.223.6#53
Jan 1 03:01:09 dnsmasq[76]: using nameserver 217.170.80.83#53
Jan 1 03:01:09 PPPoE: connect to ISP
....
Jan 1 05:11:03 pppd[112]: Terminating connection due to lack of activity.
Jan 1 05:11:03 pppd[112]: Connection terminated.
Jan 1 05:11:03 pppd[112]: Connect time 130.0 minutes.
Jan 1 05:11:03 pppd[112]: Sent 423369 bytes, received 1211354 bytes.
Jan 1 05:11:03 dnsmasq[76]: read /etc/hosts - 5 addresses
Jan 1 05:11:03 dnsmasq[76]: reading /tmp/resolv.conf
Jan 1 05:11:03 dnsmasq[76]: using nameserver 217.170.80.83#53
Jan 1 05:11:03 dnsmasq[76]: using nameserver 81.9.4.2#53
Jan 1 05:11:03 PPPoE: Disconnected
Jan 1 05:11:22 dnsmasq[76]: forwarding table overflow: check for server loops.
Jan 1 05:11:36 pppd[112]: Starting link
Jan 1 05:11:36 pppoe-relay[95]: PADO packet from 00:17:df:f3:90:1a on interface vlan1 does not have Relay-Session-Id tag
Jan 1 05:11:36 pppoe-relay[95]: PADO packet from 00:90:1a:41:da:0d on interface vlan1 does not have Relay-Session-Id tag
Jan 1 05:11:36 pppoe-relay[95]: PADO packet from 00:90:1a:41:f1:8e on interface vlan1 does not have Relay-Session-Id tag
Jan 1 05:11:36 pppoe-relay[95]: PADO packet from 00:19:a9:53:c8:1a on interface vlan1 does not have Relay-Session-Id tag
Jan 1 05:11:36 pppd[112]: PPP session is 29982
Jan 1 05:11:36 pppd[112]: Connect: ppp0 <--> vlan1
Jan 1 05:11:36 pppoe-relay[95]: PADS packet from 00:17:df:f3:90:1a on interface vlan1 does not have Relay-Session-Id tag
Jan 1 05:11:39 pppd[112]: PAP authentication succeeded
Jan 1 05:11:39 pppd[112]: peer from calling number 00:17:DF:F3:90:1A authorized
Jan 1 05:11:40 pppd[112]: Local IP address changed to 89.112.29.185
Jan 1 05:11:40 pppd[112]: Remote IP address changed to 81.9.101.119
Jan 1 05:11:40 dnsmasq[76]: read /etc/hosts - 5 addresses
Jan 1 05:11:40 dnsmasq[76]: reading /tmp/resolv.conf
Jan 1 05:11:40 dnsmasq[76]: using nameserver 81.222.223.6#53
Jan 1 05:11:40 dnsmasq[76]: using nameserver 217.170.80.83#53
Jan 1 05:11:40 PPPoE: connect to ISP
ifconfig ppp0
Code:
[admin@wlp log]$ ifconfig -a ppp0
ppp0 Link encap:Point-Point Protocol
inet addr:81.9.4.2 P-t-P:81.9.4.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING MULTICAST MTU:1492 Metric:1
RX packets:1702 errors:0 dropped:0 overruns:0 frame:0
TX packets:1472 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1211234 (1.1 MiB) TX bytes:423369 (413.4 KiB)
таблица раутинга
Code:
[admin@wlp log]$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
217.170.80.83 10.19.16.1 255.255.255.255 UGH 1 0 0 vlan1
81.9.4.2 10.19.16.1 255.255.255.255 UGH 1 0 0 vlan1
81.9.101.119 * 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0 br0
10.19.16.0 * 255.255.252.0 U 0 0 0 vlan1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default gw077-244.eltel 0.0.0.0 UG 0 0 0 ppp0
default 10.19.16.1 0.0.0.0 UG 1 0 0 vlan1
/tmp/resolv.conf (он же /etc/resolv.conf)
Code:
nameserver 217.170.80.83
nameserver 81.222.223.6
Это правильные DNS моего провайдера.
А теперь вот, что происходит:
Code:
[admin@wlp log]$ nslookup ya.ru
Server: mon1.eltel.net
Address: 217.170.80.83
Name: ya.ru
Address: 213.180.204.8
однако
Code:
[admin@wlp log]$ nslookup ya.ru 192.168.1.1
Server: wlp
Address: 192.168.1.1
Name: ya.ru
Address: 81.9.4.2
81.9.4.2 - это адрес во внутренней сетке провайдера....
192.168.1.1 - раздаётся локальным машинам как DNS сервер и в результате они всё ресолвят в этот дурацкий 81.9.4.2
С этой частью проблемы можно справиться насильно прописав одни из ДНС серверов провайдера в вебинтрефейсе. Однако тогда с компами будет всё в порядке, но из самого раутера в инет будет не выйти - похоже по проблемам раутинга.
Trace на DNS провайдера с раутера:
Code:
[admin@wlp log]$ traceroute 81.222.223.6
traceroute to 81.222.223.6 (81.222.223.6), 30 hops max, 38 byte packets
1 * * *
2 * *
тоже самое с локальной машины:
Code:
C:\Program Files\Far>tracert 81.222.223.6
Tracing route to cacti.main.eltel.net [81.222.223.6]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 73 ms 8 ms 2 ms gw077-244.eltel.net [81.9.101.119]
3 10 ms 1 ms 1 ms RT077-201.eltel.net [81.9.101.125]
4 1 ms 1 ms 3 ms te5-1.rt008-201.eltel.net [81.222.255.197]
5 5 ms 6 ms 6 ms te6-2.rt006-201.eltel.net [81.222.255.182]
6 24 ms 30 ms 19 ms gi0-1.rt088-001.eltel.net [81.222.255.210]
7 1 ms 2 ms 2 ms cacti.main.eltel.net [81.222.223.6]
Trace complete.
Умные дяденьки и тётеньки.... Помогите мне ошибочку в моей ДНК найтить....
Спасибо.
ДК