Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dns resolution problem after dc upgrades to 2008r2

Status
Not open for further replies.

bookouri

IS-IT--Management
Feb 23, 2000
1,464
US
I just just finished dcpromoing our last 2008r2 to replace 2003 server domain controllers. I have a dns problem though and can't get to the bottom of it. I dont know that this has anything to do with the new dc's but it started within a few days of the last dc promotion. I am having problems getting to machines in a trusted forest. If i ping a machine, like ping myserver it fails, but if i ping myserver.trustedforest.com it will ping. If i look at myserver in nslookup dns is appending my local forest to it, like myserver.mylocalforest.com. We have a few old applications that have to communicate across the forest trust using the machine name rather than any fully qualified name.

any suggestions would be appreciated

 
If you need to communicate to another domain then you either need to do something to indicate to the computers that is it in another domain. That usually means using an FQDN.

The other things that you could try are specifying a domain suffix search order so that multiple domains are queried in the event that the local domain does not have the appropriate record.

You could also create DNS records in your domain that point to the correct IPs. That's a bit of an ugly work around, but it should work.

Did you have WINS in your previous environment and no longer have it? That's one other possibility. Usually when you are not using FQDN you are using NetBIOS or WINS, unless it is disabled.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator
 
i was trying to avoid using wins, but one of the first things i did to try to fix the problem was to re-install wins, but it didnt seem to put things back like they were.

i managed to get the correct behavior by listing the two different domain suffixes in one of the clients ip settings, but that was a step that wasnt required before and i didnt want to resort to that.




 
I wasn't saying that you should bring WINS back, I was pointing out that if you had WINS previously and now you don't that you have lost a method of name resolution. Because of this you will be relying solely on DNS, and therefore having the DNS suffixes specified in the Domain Suffix Search Order is important (whereas before it wasn't).

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top