cannot access microsoft.com or dell.com on office workstations

Hello,

   We cannot access microsoft.com or dell.com on any of our office workstations. It does work fine on our main server (active directory and dns).

from workstations we can ping microsoft.com but it comes back with 208.109.1.1 and trying to ping dell.com gives the error could not find host dell.com

I do believe this is a dns issue, however I cannot find where the issue is.

any help?
itsup23Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

piattndCommented:
Perform the following:

start > run > cmd

nslookup microsoft.com
nslookup dell.com

Take results and paste them here (pay special attention to the server it looks at).

What are your DNS settings on the hosts?  Are you pointing to internal servers or external servers?
0
Steven CarnahanNetwork ManagerCommented:
Is it just those 2 sites?  Can you access other sites such as msn.com, yahoo.com, etc.?

The address 208.109.1.1 comes back as m1plqscweb-v05.secureserver.net in Scottsdale AZ?
0
itsup23Author Commented:
server: unknown
address: main server/dns

name microsoft.com
address: 208.109.1.1

name:dell.com
address: is blank

pointing to internal
0
Webinar: Miercom Evaluates Wi-Fi Security

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom how WatchGuard's Wi-Fi security stacks up against the competition in our upcoming webinar!

itsup23Author Commented:
yes it is just those 2 sites. other sites can be accessed
0
piattndCommented:
Can you post the results of nslookup google.com please
0
piattndCommented:
If you're getting "Server: Unknown", then you have an internal issue with reverse lookup.  That should be the name of your main DNS server IP that you have listed.

Connect to that DNS server and see if you have any entries for the Microsoft.com or dell.com domains.
0
itsup23Author Commented:
NOte: this is on workstations that are not working

nslookup - google.com

DNS request timed out
timeout was 2 seconds

server-unknown
address-main server/dns

non-authoritative answer
name: google.com
adresses:2607:f8b0:400b:80a::1009
74.125.266.105
74.125.266.103
74.125.266.98
74.125.266.96
74.125.266.99
74.125.266.101
74.125.266.110
74.125.266.100
74.125.266.97
74.125.266.102
74.125.266.104
0
piattndCommented:
Can you post the ping results when you ping the IP address of your primary and secondary DNS servers please.
0
itsup23Author Commented:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator>ping 192.168.100.113

Pinging 192.168.100.113 with 32 bytes of data:
Reply from 192.168.100.113: bytes=32 time<1ms TTL=128
Reply from 192.168.100.113: bytes=32 time=2ms TTL=128
Reply from 192.168.100.113: bytes=32 time<1ms TTL=128
Reply from 192.168.100.113: bytes=32 time<1ms TTL=128

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

C:\Users\administrator>ping 192.168.100.114

Pinging 192.168.100.114 with 32 bytes of data:
Reply from 192.168.100.114: bytes=32 time<1ms TTL=128
Reply from 192.168.100.114: bytes=32 time<1ms TTL=128
Reply from 192.168.100.114: bytes=32 time<1ms TTL=128
Reply from 192.168.100.114: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.114:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
0
piattndCommented:
ping Microsoft.com and ping dell.com

Post results here.

Also go into your DNS admin console for both primary and secondary DNS servers.  Look for the domain "Microsoft.com" and "dell.com" to be listed.

Perform

nslookup Microsoft.com 4.2.2.4
nslookup Dell.com 4.2.2.4

Post results here.  Can you also confirm if the working machines have the same DNS configuration?  Are they on the same subnet as the broken machines?  Do you have antivirus with firewall running or the windows firewall?  If so, disable them for testing purposes.
0
itsup23Author Commented:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator>ping microsoft.com

Pinging microsoft.com [208.109.1.1] with 32 bytes of data:
Reply from 208.109.1.1: bytes=32 time=92ms TTL=111
Reply from 208.109.1.1: bytes=32 time=91ms TTL=111
Reply from 208.109.1.1: bytes=32 time=91ms TTL=111
Reply from 208.109.1.1: bytes=32 time=91ms TTL=111

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

C:\Users\administrator>ping dell.com
Ping request could not find host dell.com. Please check the name and try again.

C:\Users\administrator>nslookup microsoft.com 4.2.2.4
Server:  d.resolvers.level3.net
Address:  4.2.2.4

Non-authoritative answer:
Name:    microsoft.com
Addresses:  64.4.11.37
          65.55.58.201


C:\Users\administrator>nslookup dell.com 4.2.2.4
Server:  d.resolvers.level3.net
Address:  4.2.2.4

Non-authoritative answer:
Name:    dell.com
Addresses:  143.166.83.38
          143.166.224.244


no entries for micorsoft or dell on dns
yes machines are on the same subnet
only my main server .113 does microsoft and dell work
0
Steven CarnahanNetwork ManagerCommented:
Try changing the DNS server on one of the "broken" systems to 8.8.8.8 or 8.8.4.4 and try again. If that works then put your original back as the primary and one of the above as secondary and try access again.
0
piattndCommented:
Doing what Pony10us is suggesting will test external DNS, but will not fix your internal DNS once you come back to the internal DNS.  You may even have a cached DNS entry for the hosts and appear to be fixed, when in reality DNS is still incorrect internally.

The next step is to check your root hints or forwarders.

Go to the primary and secondary DNS servers to check forwarders.  Look for anything specific to Microsoft.com or dell.com.  If nothing, check root hints.

This document should help in doing that:

http://technet.microsoft.com/en-us/library/ff807391(v=ws.10).aspx

Correction:

Check the bottom of the link above for the IP addresses for the root hints:

The following is the default list of root hints.
• a.root-servers.net. 198.41.0.4


• b.root-servers.net. 192.228.79.201


• c.root-servers.net. 192.33.4.12


• d.root-servers.net. 128.8.10.90


• e.root-servers.net. 192.203.230.10


• f.root-servers.net. 192.5.5.241


• g.root-servers.net. 192.112.36.41


• h.root-servers.net. 128.63.2.53


• i.root-servers.net. 192.36.148.17


• j.root-servers.net. 192.58.128.30


• k.root-servers.net. 193.0.14.129


• l.root-servers.net. 199.7.83.42


• m.root-servers.net. 202.12.27.33
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
itsup23Author Commented:
This is working now. on my primary dns the forwarders had 8.8.8.8 as secondary on once it was moved up both sites now work.

Thanks
0
piattndCommented:
Glad you got it working.  GL to you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Internet Protocols

From novice to tech pro — start learning today.