Nếu như vậy thì bạn cứ để mọi người chạy ổn định trong 8.8.8.8 đi.
Bao giờ configure & test okie hết thì hẵng trỏ qua 192.168.111.220. Sao lại mang Client ra để test vậy ?

Bạn tham khảo 1 trường hợp tương tự nhé. Lí giải rất rõ ràng. Ngày trước mình cũng đã từng gặp chuyện này

Questions

I have a user on Windows 7 that is trying to access a local server with a DNS name of windows.cs. We have two internal DNS servers. The DHCP server assigns users the two internal DNS servers as primary and secondary and then our ISPs DNS as a tertiary DNS server.

Every now and then, the user can't access the website at windows.cs. If I ping it, it says it can't resolve the host name. I flush the DNS cache, and then when I display the dns cache it has the following:

windows.cs - Name does not exist

Yet if I use nslookup, which by default queries the primary DNS server (our internal one) and I query windows.cs, it returns the correct IP address.

So why can't Windows resolve the hostname using ping, but it can when using the nslookup tool? And how do I fix this?

Repply

It's appears from what you're saying that the request for windows.cs is going to the ISPs DNS server now and again. The nxdomain result is then probably cached by Windows' DNS client, and thus used for any retries with a web browser, ping etc. Clearing the cache (ipconfig /flushdns) should force the Windows DNS client to retry the query, but there's no guarantee it won't go to the ISP DNS server again.

The reason ping can't resolve the hostname but nslookup can is because nslookup a low level tool that bypasses the Windows DNS client. It uses whatever DNS server you tell it to (the first one by default), and does the query on the fly. You can change the DNS server it queries by typing server <host> from the nslookup prompt, where host is the IP or FQDN.

The Windows DNS client however will only do queries for entries that are not in its cache (or have expired). Otherwise it returns the cached result.

It's not immediately apparent why the Windows client is using the ISP DNS server. Perhaps it could not resolve the local server recently (due perhaps to being on another network), perhaps the local server was returning errors. Or perhaps it is not ordered correctly under Advanced TCP/IP settings > DNS.

Personally I prefer to only use local DNS server addresses on workstations (propagated by DHCP), to simplify configuration and avoid issues like this. I'd be curious to know the rationale behind setting the ISPs DNS server on desktops. I can't image their being any valid performance reasons and as far as redundancy goes two is enough on most networks (if not add a third). 

 

Mình nghĩ chỉ cần để 1 cái dns 192.168.111.220
Sử dụng chức năng Forwarder DNS để client có thể query những domain không có trong List Zones.
Lúc này khi bạn truy cập tên miền nội bộ thì dns sẽ tìm kiếm trong các zones có trongl list.nếu không có mới Forward ra ngoài.

Thân.