Ask a new question

Trying to connect to www.mol.usmc.mil DNS request timed out

Page just keeps loading.

C:\Users\Alexander>nslookup www.mol.usmc.mil
Server:  rdns-lb-01.hawaii.rr.com
Address:  24.25.227.55

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to rdns-lb-01.hawaii.rr.com timed-out

C:\Users\Alexander>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Alexander-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hawaii.rr.com

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : hawaii.rr.com
   Description . . . . . . . . . . . : Killer e2200 Gigabit Ethernet Controller
(NDIS 6.30)
   Physical Address. . . . . . . . . : 8C-89-A5-0F-24-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2605:e000:efc0:4b:4890:6de7:3b17:694c(Pre
ferred)
   Lease Obtained. . . . . . . . . . : Sunday, June 29, 2014 8:41:09 PM
   Lease Expires . . . . . . . . . . : Monday, July 7, 2014 8:14:33 AM
   Link-local IPv6 Address . . . . . : fe80::781a:b88f:baad:fccc%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 66.91.114.9(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.248.0
   Lease Obtained. . . . . . . . . . : Sunday, June 29, 2014 8:41:08 PM
   Lease Expires . . . . . . . . . . : Tuesday, July 1, 2014 11:54:11 PM
   Default Gateway . . . . . . . . . : 66.91.112.1
   DHCP Server . . . . . . . . . . . : 142.254.190.81
   DHCPv6 IAID . . . . . . . . . . . : 462195109
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-16-10-6A-6C-71-D9-B3-A5-52

   DNS Servers . . . . . . . . . . . : 24.25.227.55
                                       209.18.47.61
                                       24.25.227.53
   NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 6C-71-D9-B3-A5-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 6C-71-D9-B3-CB-E1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8723AE Wireless LAN 802.11n PC
I-E NIC
   Physical Address. . . . . . . . . : 6C-71-D9-B3-A5-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:383f:2d15:bda4:8df6(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::383f:2d15:bda4:8df6%17(Preferred)
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 536870912
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-16-10-6A-6C-71-D9-B3-A5-52

   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.hawaii.rr.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : hawaii.rr.com
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Answer
Answer

 11   158 ms   131 ms   131 ms  208.46.37.38

That's where my tracert was stopped too, so no problem there.  Did you try using the IP address in IE--to make sure you have connectivity to that server by HTTP? 

But also note that your DNS is finding the canonical host, so you could try it by name too... same issue with certificate but again understandable.

Then your only problem is still getting a DNS lookup by name using your ISP's DNS.  So, tell your ISP about the problem and see if they will fix it for you.  Alternatively you could switch to Google's DNS or find a different primary DNS which does know about the problem host.

In fact, since you can do the lookup for the canonical host you can probably find its Name server and then if necessary use that to do the lookup for the problem host.  Here's how that could work:  enter just nslookup (with no operands) to get into its interactive mode.

Once you are in nslookup in its interactive mode:

> set type=NS
> mol.usmc.mil
Server:  UnKnown
Address:  192.168.1.2

usmc.mil
        primary name server = usmcdns1.usmc.mil
        responsible mail addr = security.mcnosc.usmc.mil
        serial  = 2014070100
        refresh = 3600 (1 hour)
        retry   = 600 (10 mins)
        expire  = 604800 (7 days)
        default TTL = 3600 (1 hour)

> exit

C:\windows\system32>nslookup www.mol.usmc.mil usmcdns1.usmc.mil
Server:  usmcdns1.usmc.mil
Address:  192.156.71.120

Name:    mol.usmc.mil
Address:  205.110.196.213
Aliases:  www.mol.usmc.mil

So, that way you could have a name server which definitely knew about the problem host and one which was not related to Google or any other third-party lookup service.  But it probably wouldn't be useful for much of anything but that lookup.   ; )

In fact, though, you might find that just getting that DNS server involved with a lookup might provide a clue to your normal DNS lookup.  (I don't know but do know there can be lots of caching going on along the path.)  TBD.

Another possibility would  be adding the lookup of the problem host to your HOSTS file.

 

Good luck

Robert
---

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated February 12, 2018 Views 942 Applies to: