ttnetworks
asked on
Visa DNS Lookup
My Windows Vista Enterprise x64 Edition has some weird DNS issues. If I try to connect to a Remote Desktop for example, I punch in machine.domain.com and it comes back straight away saying cannot find server.
I go to a command prompt, type in:
C:\Users\Andrew>nslookup machine.domain.com
Server: server.domain.com
Address: 192.168.4.3
Name: machine1.domain.com
Address: 192.168.4.14
Aliases: machine.domain.com
Which works fine, no delay, just performs a DNS lookup straight away, if I then immediately type:
C:\Users\Andrew>ping machine.domain.com
Ping request could not find host machine.domain.com. Please check the name
and try again.
C:\Users\Andrew>
WHY!!!???
The DNS lookup clearly works because NS Lookup is OK, so why won't Windows bloody lookup the DNS name and do what it's supposed to do ?
Typing ipconfig /flushdns at the command prompt seems to fix it, and it then works properly, but I should not have to do that. This is basic networking Microsoft ?!
Thanks
Andrew
I go to a command prompt, type in:
C:\Users\Andrew>nslookup machine.domain.com
Server: server.domain.com
Address: 192.168.4.3
Name: machine1.domain.com
Address: 192.168.4.14
Aliases: machine.domain.com
Which works fine, no delay, just performs a DNS lookup straight away, if I then immediately type:
C:\Users\Andrew>ping machine.domain.com
Ping request could not find host machine.domain.com. Please check the name
and try again.
C:\Users\Andrew>
WHY!!!???
The DNS lookup clearly works because NS Lookup is OK, so why won't Windows bloody lookup the DNS name and do what it's supposed to do ?
Typing ipconfig /flushdns at the command prompt seems to fix it, and it then works properly, but I should not have to do that. This is basic networking Microsoft ?!
Thanks
Andrew
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you have a secondary DNS server configured for your workstation that might be answering some of your queries negatively? If so, try querying them both from nslookup in turn and check they're saying the same thing.
in cmd line type ipconfig /flushdns and try again.
ASKER
Yolam,
Read the last paragraph of my question.
Thaks
Read the last paragraph of my question.
Thaks