Learn how to a build a cloud-first strategyRegister Now


Not able to ping machines in same domain while using a DNS Suffix Search List

Posted on 2004-11-24
Medium Priority
Last Modified: 2010-08-05
We are using a .vbs script to configure our client dns suffix search lists.  I have found that while using a dns suffix search list, the primary DNS suffix is not used.  I have manually added the primary DNS suffix search list to the script however that dns suffix does not 'stick'.  The only way I have found to connect to a machne in my domain is by using the FQDN.  Here is an example.
We are running 2003 AD
The domain I am in is 123.abc.com
The DNS suffixes in the seach list .vbs script are:
I can ping anything in 456.abc.com and 789.abc.com by using host name only.  I cannot ping anytihing in 123.abc.com unless I use the FQDN.  
I have tried entering 123.abc.com manually in my DNS suffix search list to no avail.  An ipconfig /all shows my Primary DNS as 123.abc.com and 456.abc.com & 789.abc.com show in the DNS suffix search list.  Wierd...
Question by:billzbubs
LVL 17

Expert Comment

by:Jared Luker
ID: 12669463
Sounds like a DNS problem to me.  Are you sure your reverse lookup zones are configured correctly?

Expert Comment

ID: 12669470
Looks like a Browsing and DNS problem.   Make sure you don't have Netbios disabled on machines that require FQDN.  Install a WINS server and set all the machines to use it for the WINS server.  

Author Comment

ID: 12669567
I am trying to resole host name to IP not IP to host name so it is not a revers DNS issue.  One of the great points of DDNS is to get rid of crappy WINS so that is not an option either.
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

LVL 17

Expert Comment

by:Jared Luker
ID: 12669733
Are you able to use NSLOOKUP at all?

Author Comment

ID: 12669864
OK, I found it.  It was a 2003 Group Policy that was stepping on the .vbs script.  Since the GPOs in 2003 to configure DNS Suffix Search lists only work on XP/2003 clients, we will have to use St. Bernard to deploy the .vbs script only to our W2K clients and rely on 2003 GPOs to hook up the XP and 2003 machines.  thanks for the assistance anyway.

Accepted Solution

modulo earned 0 total points
ID: 13175132
PAQed with points refunded (300)

Community Support Moderator

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
LinkedIn blogging is great for networking, building up an audience, and expanding your influence as well. However, if you want to achieve these results, you need to work really hard to make your post worth liking and sharing. Here are 4 tips that ca…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question