DNS timing out when trying to connect to thescripts.com - works from other locations.
One of my coworkers was trying to access thescripts.com, and was unable to. But if he remotes to his home computer he can get in fine.
I did an nslookup, and it looks like this:
Z:\>nslookup thescripts.com
Server: covwin4.clawnet.local
Address: 192.168.1.4
DNS request timed out.
timeout was 2 seconds.
*** Request to covwin4.clawnet.local timed-out
So I did a web based whois and came up with this for authoritative servers:
Domain servers in listed order:
NS1.SOFTLAYER.COM
NS2.SOFTLAYER.COM
An nslookup specifying either of those servers works:
Z:\>nslookup thescripts.com NS1.SOFTLAYER.COM
Server: ns1.softlayer.com
Address: 66.228.118.8
Name: thescripts.com
Address: 75.126.163.34
Z:\>nslookup thescripts.com NS2.SOFTLAYER.COM
Server: ns2.softlayer.com
Address: 66.228.119.9
Name: thescripts.com
Address: 75.126.163.34
Looking in our DNS server - which is a Windows Server 2003 system running the default DNS package, I find these entries under thescripts.com:
Name Server (NS) ns2.thescripts.com.
Name Server (NS) ns1.thescripts.com.
If I delete those, they are recreated when I next try to lookup the ip for thescripts.com. They come back the same. Of course, they should - those are the correct dns servers.
So why can't I get DNS for this site?
I did an nslookup, and it looks like this:
Z:\>nslookup thescripts.com
Server: covwin4.clawnet.local
Address: 192.168.1.4
DNS request timed out.
timeout was 2 seconds.
*** Request to covwin4.clawnet.local timed-out
So I did a web based whois and came up with this for authoritative servers:
Domain servers in listed order:
NS1.SOFTLAYER.COM
NS2.SOFTLAYER.COM
An nslookup specifying either of those servers works:
Z:\>nslookup thescripts.com NS1.SOFTLAYER.COM
Server: ns1.softlayer.com
Address: 66.228.118.8
Name: thescripts.com
Address: 75.126.163.34
Z:\>nslookup thescripts.com NS2.SOFTLAYER.COM
Server: ns2.softlayer.com
Address: 66.228.119.9
Name: thescripts.com
Address: 75.126.163.34
Looking in our DNS server - which is a Windows Server 2003 system running the default DNS package, I find these entries under thescripts.com:
Name Server (NS) ns2.thescripts.com.
Name Server (NS) ns1.thescripts.com.
If I delete those, they are recreated when I next try to lookup the ip for thescripts.com. They come back the same. Of course, they should - those are the correct dns servers.
So why can't I get DNS for this site?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Didn't end up finding an ideal solution... however, scorpiia's suggestion was helpful, even if not exactly what I was looking for.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER