Cerulean
[H]F Junkie
- Joined
- Jul 27, 2006
- Messages
- 9,476
Greetings,
Running a Windows 2008 R2 x64 server (10.0.255.3). Not sure if it is just MediaCom being slow and wack, but a lot of websites that I first load do not load their stylesheets until I refresh/reload the page with F5. In addition, some 15-30 minutes ago, I couldn't pull up any website other than google.com and yahoo.com. I did nslookup and tracert on sites like orderdis.com (main company website hosted by DreamHost) and dreamhost.com, and got an error like:
I'm somewhat suspicious that Windows DNS/DHCP is the culprit, or I don't know. Our pfSense router is at 10.0.255.1. DHCP tells clients that the default gateway ("Router" in Windows DHCP service) is 10.0.255.1, DNS is 10.0.255.3. Right now I can apparently browse the internet fine.
CEO sent me a complaint via e-mail about how unsatisfyingly slow and getting 404 errors on certain webpages (like aa.com [American Airlines] -- and obviously, a website for a company as big as American Airlines should not be giving 404/website not found messages in IE). I'm wondering if perhaps OpenDNS may be the culprit too; pfSense box (10.0.255.1) is configured to use 208.67.222.222 and 208.67.220.220 for DNS through WAN.
EDIT: Ok, aa.com is not coming up again. tracert sure takes its time as it tries to resolve each hop.
EDIT2: Ok, aa.com comes up like half the time, so it's really hard to get any good nslookup/tracert/ping results to indicate a problem somewhere
EDIT3: I am connected with my laptop from my apartment via VPN. pfSense box (10.0.255.1) serves VPN. Here is my ipconfig and an nslookup on opendns.com
Here is the ipconfig and nslookup opendns.com from the Windows server (10.0.255.3):
Why do I get different results? And is this Windows server just too slow to quickly serve DNS name resolution queries?
Running a Windows 2008 R2 x64 server (10.0.255.3). Not sure if it is just MediaCom being slow and wack, but a lot of websites that I first load do not load their stylesheets until I refresh/reload the page with F5. In addition, some 15-30 minutes ago, I couldn't pull up any website other than google.com and yahoo.com. I did nslookup and tracert on sites like orderdis.com (main company website hosted by DreamHost) and dreamhost.com, and got an error like:
C:\Users\Administrator>tracert orderdis.com
Unable to resolve target system name orderdis.com.
I'm somewhat suspicious that Windows DNS/DHCP is the culprit, or I don't know. Our pfSense router is at 10.0.255.1. DHCP tells clients that the default gateway ("Router" in Windows DHCP service) is 10.0.255.1, DNS is 10.0.255.3. Right now I can apparently browse the internet fine.
CEO sent me a complaint via e-mail about how unsatisfyingly slow and getting 404 errors on certain webpages (like aa.com [American Airlines] -- and obviously, a website for a company as big as American Airlines should not be giving 404/website not found messages in IE). I'm wondering if perhaps OpenDNS may be the culprit too; pfSense box (10.0.255.1) is configured to use 208.67.222.222 and 208.67.220.220 for DNS through WAN.
EDIT: Ok, aa.com is not coming up again. tracert sure takes its time as it tries to resolve each hop.
EDIT2: Ok, aa.com comes up like half the time, so it's really hard to get any good nslookup/tracert/ping results to indicate a problem somewhere
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>nslookup aa.com
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: aa.com
Address: 144.9.72.134
C:\Users\Administrator>tracert aa.com
Tracing route to aa.com [144.9.72.134]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.255.1
2 7 ms 7 ms 7 ms 10.172.54.1
3 5 ms 7 ms 7 ms 172.30.3.237
4 7 ms 7 ms 7 ms 172.30.3.213
5 12 ms 11 ms 11 ms 12.94.137.21
6 24 ms 22 ms 23 ms cr2.kc9mo.ip.att.net [12.122.150.138]
7 23 ms 23 ms 23 ms cr1.dlstx.ip.att.net [12.122.28.85]
8 78 ms 49 ms 34 ms 12.122.212.9
9 21 ms 20 ms 21 ms 192.205.37.126
10 23 ms 23 ms 20 ms 0.ae1.xl3.dfw7.alter.net [152.63.96.46]
11 22 ms 23 ms 23 ms 0.xe-3-0-0.xt3.dfw9.alter.net [152.63.0.49]
12 24 ms 22 ms 22 ms gigabitethernet6-0-0.gw14.dfw9.alter.net [152.63
.96.65]
13 24 ms 23 ms 23 ms eds-planotx-gw.customer.alter.net [63.125.131.2]
14 23 ms 23 ms 24 ms 192.85.47.241
15 27 ms 24 ms 23 ms 192.85.58.10
16 25 ms 24 ms 24 ms www.aa.com [144.9.72.134]
Trace complete.
C:\Users\Administrator>ping aa.com
Pinging aa.com [144.9.72.134] with 32 bytes of data:
Reply from 144.9.72.134: bytes=32 time=23ms TTL=243
Reply from 144.9.72.134: bytes=32 time=24ms TTL=243
Reply from 144.9.72.134: bytes=32 time=24ms TTL=243
Reply from 144.9.72.134: bytes=32 time=23ms TTL=243
Ping statistics for 144.9.72.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms
C:\Users\Administrator>
EDIT3: I am connected with my laptop from my apartment via VPN. pfSense box (10.0.255.1) serves VPN. Here is my ipconfig and an nslookup on opendns.com
Code:
PPP adapter Data Imaging Supplies:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Data Imaging Supplies
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.255.192(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
Primary WINS Server . . . . . . . : 10.0.255.3
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Users\Qwerty>nslookup opendns.com
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: opendns.com
Address: 208.69.38.160
Here is the ipconfig and nslookup opendns.com from the Windows server (10.0.255.3):
Code:
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : echo
Primary Dns Suffix . . . . . . . : orderdis.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : orderdis.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-14-38-BD-33-35
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.255.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.0.255.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server Adapter #2
Physical Address. . . . . . . . . : 00-14-38-BD-33-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{EB43A2CB-114A-4A53-B93A-940B886BB66C}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{E1222507-0B6C-4817-BEE2-0DB566476154}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
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
C:\Users\Administrator>nslookup opendns.com
Server: localhost
Address: 127.0.0.1
Name: opendns.com
Address: 208.69.38.150
C:\Users\Administrator>
Why do I get different results? And is this Windows server just too slow to quickly serve DNS name resolution queries?
Last edited: