DNS faqat Windows 7-da nslookup-ga javob beradi

Men AD (2008R2) da qiziq bir DNS muammosiga ega bo'laman va bu disk raskadrovka usulini topa olmayapman. Odatda buyruq qatoridan harakat qilaman

ping 
then I get the reply that the hostr isn't found. But when I do
nslookup 
I get the correct response from my DNS with proper AAAA and A records. Anyone has an idea what could cause this?

Mijozlar mashinalarida Windows 7 Enterprise ishlaydi.

4

6 javoblar

HOSTS va LMHOSTS ning hech qanday kulgili joyi yo'qligiga ishonch hosil qiling. nslookup to'g'ridan-to'g'ri DNS serveriga murojaat qilib ishlaydi, nom piksellar sonini esa operatsion tizim orqali amalga oshiradi. Bu shuni anglatadiki, sizning HOSTS faylingiz vintlangan bo'lishi mumkin yoki Winsock va boshqalardagi korruptsiya mavjud.

Biz IPv4 va IPv6 bilan o'ynamoqdamiz, shuning uchun host-4 va ping-host -6-ga ping-ping qo'yiladi.

WINS/NetBIOS-ni o'chirib qo'yish ham mumkin

alt text

2
qo'shib qo'ydi

Windows 7 Windows Xavfsizlik devoridagi Ping javobini o'chirib qo'yadi. Uni barcha mijoz mashinalarida ishga tushirishingiz kerak. Bu guruh siyosati orqali amalga oshirilishi mumkin emasligiga ishonchimiz komil emas. Bu erda

1
qo'shib qo'ydi
Savolga ko'ra, uy egasi topilmasa, so'rov muddati tugamaguncha emas. Bu DNS-piksellar bilan bog'liq muammo.
qo'shib qo'ydi muallif ta.speot.is, manba
Yaxshi, ba'zi DirectAcces qoidalari orqali yoqadi
qo'shib qo'ydi muallif Jus12, manba

Menda faqat bitta muammo bor edi. Men uchun bu muammo bir necha DNS serverlari aniqlanganligi tufayli yuzaga keldi. Mening IPv4 sozlamalarim asosiy DNSni yo'riqchimga o'rnatgan va ikkilamchi DNS esa Google DNS serveriga o'rnatgan DHCP-ga o'rnatildi. Buyurtma ahamiyatga ega bo'lmasada DHCP orqali taqdim etilgan DNS-serverdan foydalanishda muammo hal qilindi. DNS serverlarini qayta qo'shish muammoga sabab bo'ladi.

Men buning asosiy sababini tushunmayapman. Lekin, ehtimol siz uchun bu masala.

0
qo'shib qo'ydi

Previous comments are right. I would simply add that there MAY be a sequence for name resolution. At least, this exists under Linux as a file named /etc/nsswitch. By default, a local HOST file will resolve names BEFORE invoking a name server. As for the actual IP addresses of the name servers, those are setup in Control Panel -> Network

Odatda HOSTS fayl C: \ WINDOWS \ SYSTEM32 \ DRIVERS \ ETC ostida joylashgan

Ushbu fayl bloknot yordamida tuzilishi mumkin. Ushbu faylni har doim men turli xil virtual Windows serverlarida ishlataman.

0
qo'shib qo'ydi

Men o'zimning mahalliy tarmoqni domen va statik DNS yozuvlarini ushbu domenga joylashtirish uchun mening yo'riqnoma DHCP sozlamalarini o'zgartirish orqali hal qildim.

Shu bilan birga, turli xil alomatlar va turli xil echimlar (ro'yxatga olish kitobi o'zgarishi) bo'lgan o'xshash bir masalani tasvirlaydigan bir qancha forumlar topdim, shuning uchun muammodan batafsil ajratish uchun muammoimni batafsil tushuntirmoqchiman.

Mening mavzuim

Yaqinda yangi yo'riqnoma (Mikrotik) oldim va har bir xostni o'zimning tarmog'imda statik IP-manzilga belgilab qo'ydim va har bir kompyuterga mahalliy DNS hostname (va faqat bitta hostname) berishni sozlaganman. Bu UNIX/Linux/Mac OS Xdan yaxshi ishladi, ammo Windowsda bu muammo yuzaga keldi.

Windowsda men ularni bir necha hostlari nomidan ping qila olmadim, garchi men ularni nslookup orqali qidirishar va ularni IP bilan ping qilsam:

C:\>nslookup router
Server:  router
Address:  192.168.22.1

Non-authoritative answer:
Name:    router
Address:  192.168.22.1


C:\>ping router
Ping request could not find host router. Please check the name and try again.

C:\>ping 192.168.22.1

Pinging 192.168.22.1 with 32 bytes of data:
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.22.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>nslookup overkill
Server:  router
Address:  192.168.22.1

Non-authoritative answer:
Name:    nas_server
Address:  192.168.22.5

Lekin g'alati, ba'zilari ishlagan:

C:\>ping nas_server

Pinging nas_server [192.168.22.5] with 32 bytes of data:
Reply from 192.168.22.5: bytes=32 time<1ms TTL=64
Reply from 192.168.22.5: bytes=32 time<1ms TTL=64
Reply from 192.168.22.5: bytes=32 time<1ms TTL=64
Reply from 192.168.22.5: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.22.5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>

Bundan tashqari, Wiresharkni tekshirish uchun foydalanar edim va ping komandasi faqat har qanday DNS paketiga sabab bo'lmaganligini aniqladi. rel = "nofollow noreferrer"> NetBIOS ismi xizmati paketlari. Bu yo'riqnoma uchun muvaffaqiyatsiz bo'ladi, lekin mening NAS serverim uchun muvaffaqiyatli bo'ladi (chunki NAS Samba ishlayotgan edi). Nslookup DNS-ni ishlatdi, shuning uchun hamma narsa uchun ishladi.

Wireshark capture from ping: Wireshark Capture from ping

Ildiz muammo, ba'zi holatlarda (masalan, hostda domen mavjud bo'lmaganda) Windowsning NetBIOS Name Service o'rniga DNS-dan foydalanishi bo'ldi.

Mening biznesim

Eslatma: displeylar yo'riqnoma konfiguratsiya ekranimdan olingan, lekin ular umumiy tushunchalarni tasvirlaydi.

I configured my DHCP server to tell all hosts that they were part of a domain: DHCP config

Then I configured all my static DNS entries to place all hosts in this domain: Static DNS entry

Keyinchalik Windows'dagi barcha DHCP/DNS ma'lumotlarini o'chirib tashladim:

C:\>ipconfig /release
C:\>ipconfig /renew
C:\>ipconfig /flushdns

Va hamma narsa ishladi!

C:\>ping router

Pinging router.localnet [192.168.22.1] with 32 bytes of data:
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64
Reply from 192.168.22.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.22.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
0
qo'shib qo'ydi

I've run into Vista systems caching null dns entries if a dns server was not available. Running "ipconfig /flushdns" cleared them out. Depending on what the root cause is this might only be a bandaid fix but have a look at disabling the caching of negative dns results. There are decent instructions here

0
qo'shib qo'ydi