rockafella77
asked on
DNS Lookup issue.
Currently we have 3 domains on our network, when I am on my main dns parent server and try to do a nslookup on another server in a different domain by IP nslookup works correctly and I get server2.domain2.com however when I do a nslookup on the same server using just the name "server2" it resolves back server2.domain1.com. I am not sure why it is resolving with a different domain and would like to be able to access the devices in this domain by just using the short name and not the IP or FQDN and wondering if anyone had any thoughts.
thanks
thanks
ASKER
Unpon further testing when I try to do a nslookup on my third domain i get *.*domain3.com can't find "servername" : non-existent domain, but I do see the domain in my list, so I don't think the above will resolve my issue
So servername.domain3.com exists? And you want to just lookup servername?
If that is the case, then as long as you have a DNS Suffix for domain3.com it should work (and it's set to Append Suffixes in Order.
Chris
ASKER
I think i tried what you mentioned but still no success I have domain1, domain2, domain3 each with there own dns server (1,2,3) Domain one is the parent. When I do a nslookup on server1 and lookup server3, i get server1.domain1.com can't find server3: Non-existent domain, however when i got to DNS on server1 I see all the domain under forward lookup zones and all the host within them. Sorry for the poor explaination.
The FQDN for each works though? From that server you can ping server1.domain3.com?
Chris
ASKER
yeah if I am using the FQDN I can ping and resolve across the board
If you could try this in nslookup:
C:\> nslookup
> set srchlist=domain1.com/domai
> servername
That tells nslookup itself to search suffixes instead of just the DNS Client. If that works then we just need to look into a problem with the network adapter settings.
Chris
ASKER
That works, I am just confused about the network adapter settings as I have never had to do this before
Okay cool, at least it'll do what we want eventually.
Here's a Screenshot of what we're looking to set. It's Vista, but it's not too different from everything else.
Chris
Suffixes.jpg
ASKER
that works, however it was never setup before like this, and it was working until one our dns servers was replaced. Is there a way of setting this up on the DNS servers?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will take your answer for it, I just don't know enough to understand yet, I know I didn't have to have those network adapters settings before, and my wins server is still inplace, and after replacing one of my dns servers I now have to makes some major changes.
thanks for you help
thanks for you help
ASKER
I wish one day to reach the dns level that he had
thanks
thanks
Well hold on. Give the WINS Forwarding a try first, it's possible that's all it ever was.
Here's where it's set.
Chris
WINSForwarding.jpg
ASKER
yeah i have that but what i know realize is that I am not even able to browse my domains via network neighborhood, windows network. from either server in different domains, I am thinking of doing more research and posing a new question with alot more detail
Okay, you need to focus the question on WINS and Network Browsing to chase that one. Network Neighbourhood is entirely based on those and doesn't touch on DNS at all.
Chris
ASKER
thanks for your help, I really appreciate
Hey,
You must add each domain you want to resolve by name only for to the DNS Suffix Search List.
There are a number of different ways you can do that, perhaps the most useful would be Group Policy:
Computer Configuration \ Administrative Templates \ Network \ DNS Client
Then set a value for "DNS Suffix Search List". e.g. domain1.com,domain2.com,do
If you just want to check this does what you want open up the Properties for TCP/IP on your network connection, select Advanced, then DNS, then add the Suffixes to the Search List there.
HTH
Chris