Re: DNS resolution not working



Also noticed that these computers that fail to lookup, only fail on 1
specific server.

So 4 computers fail to look up a dns record for one specific server, on any
application other than nslookup. These lookups can be fqdn, and still fail.
The computers never do it at the same time and are random, when it happens
you can ping any other server, connect to any local of external website,
except for this one server, from the computer that is failing, all other
computers work fine.

To get the PC to start working correctly again requires you to do either
restart, or just do a release and renew with ipconfig.

DNS is working, as nslookup works from the affected pcs.

"David" wrote:

Cant ping with a FQDN.

"Robert L. (MS-MVP)" wrote:

Can you ping the computer by using FQDN?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE1E2047-7445-4499-94C3-469D32A430C0@xxxxxxxxxxxxxxxx
Hi,

I have a problem with DNS resolution on a few desktops on our network.
They
randomly stop being able to resolve DNS names within applications other
then
nslookup.
This is what works and doesnt.
nslookup: works fine, resolves the host names.
ping: fails on resolving the host name, but will ping if ip address is
entered.
ie: fails on host name, works on ip.

Tried ipconfig /flushdns, doesnt fix the problem. But "ipconfig /release &
ipconfig /renew" fixes the problem for a while.

The DNS is working fine, as nslookup works and other computers on the
network are not affected. the problem appears to be location on the
desktop,
but I am not sure what is causing it, driver problem? I have searched for
this and found a few other peopel else where have had a similar problem
but
no solution was found.

Any help would be appriciated.

Thanks


.



Relevant Pages

  • Re: No DC in Active Directory
    ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS. ... The second server ... the first server now shows no DCs in the Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client computer internet connection problems
    ... subnet, Default Gateway, correct DNS entry/ies). ... his TCP/IP Configuration settings then he is not going to be able to join ... O*N*L*Y the internal DNS Server IP Address..... ... join the computers to my server domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharing a drive on my computer with others
    ... SBS 2003 needs to manage DNS and really likes to manage DHCP, ... You need to use the wizards on the SBS server to get it all working properly. ... I can't ping any of the computers within the domain. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Replacing Win2000 Domain controllers
    ... Normally you can rename a computer in the domain without any problem, maybe the account did not have the correct rights in AD. ... If you remove it give time for replication and also check that all entries from the DNS management console are deleted and also from the DNS zone properties under the Name server tabs, if it was a DNS server. ... I've tried renaming computers in the domain before and ...
    (microsoft.public.windows.server.migration)
  • Re: Error adding computers to domain
    ... > add Windows 2000 computers to a domain. ... > all because that function isn't necessary on that server. ... While not required by the server, the clients would certainly see a benefit. ... ever use an ISP's DNS server. ...
    (microsoft.public.win2000.advanced_server)

Quantcast