Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


DNS problems with different domains

Posted on 2005-03-03
Medium Priority
Last Modified: 2010-03-18
We have 3 domains. DOMAIN1.COM, DOMAIN2.COM, DOMAIN3.COM. Domain's 1 and 2 are Active Directory domains each running DNS for their domain. DOMAIN3 is a domain with only an Exchange server named EXCHANGESRV. On the DNS servers in DOMAIN1 & DOMAIN2 I added a host record for EXCHANGESRV. When a client in DOMAIN1 tries to ping EXCHANGESRV it resolves to EXCHANGESRV.DOMAIN1.COM and can ping the server. For clients with static addresses (including DNS) who do not login to any domain try to ping EXCHANGESRV it fails and cannot find host. However, if their DNS server is in DOMAIN1.COM they can sucessfully ping EXCHANGESRV.DOMAIN1.COM.  In Outlook where the server name is specified as the NETBIOS name EXCHANGESRV clients cannot login because it can't resolve EXCHANGESRV.
Some of these static clients are Mac's and some are PC's. Is there a way to have them all resolve EXCHANGESRV without setting them for DHCP as they are on a different subnet and there is no DHCP server available.

Question by:bhatok
  • 2
  • 2
LVL 15

Expert Comment

by:Joseph Hornsey
ID: 13456504

Try manually adding a host record for EXCHANGESRV in the domains whose clients can't ping it.


Author Comment

ID: 13463172
I have manually added a host record for EXCHANGESRV in the DNS servers of the clients who can't ping. They still cannot ping EXCHANGESRV, but by adding the record they can then ping EXCHANGESRV.DOMAIN.COM

Since Outlook is looking for EXCHANGESRV, they still cannot access email unless I edit the HOSTS file with the unqualified name EXCHANGESRV and the IP of the server.
LVL 15

Accepted Solution

Joseph Hornsey earned 500 total points
ID: 13464375

I'm not thinking too clearly... I don't know why this isn't just coming to me, because it's a really simple solution.  How about this... delete the host record and add a CNAME record of EXCHANGESRV and point it to EXCHANGESRV.DOMAIN1.COM (or wherever the Exchange server is).

Actually, I just noticed that you said that the problem is with users who do not log in to a domain.  When the computer is a member of the domain, it automatically appends the domain to the end of a host query (if it's not a query for an FQDN) which is why domain users work okay.  If the computer's not in the domain, try appending the domain name to the end of the connection on those computers.  Go to your Network Connections and then the properties of the Local Area Connection.  Go to the TCP/IP properties and cilck on Advanced.  Go to the DNS tab and there should be a space to add a DNS suffix for the connection.  Put in whichever domain they should be using and give it a whirl.

This is a setting in DHCP, too if you want to automate it.


Author Comment

ID: 13476304
Thanks for your help. I statically added the domain suffix to the PC's who weren't using DHCP and it let Outlook find the server.

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

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

Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

577 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