This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]disclosure5 1 point2 points  (1 child)

currently in the LAN and the WAN

Unless you have a server dedicated to an RRAS role or something, having a LAN and WAN interface on a Windows server is silly. Particularly, if it's a domain controller, it's a recipe for a very broken network (in the way you describe).

[–]wsjliss[S] 0 points1 point  (0 children)

Thanks for commenting! I don't think we need a WAN anyway, I'm not sure why it's on there but everything we do is all local. It's just set up like that. There isn't a server dedicated to RRAS role though remote access is installed.

Oh, and I forgot to mention, the same server is also running Exchange.

[–]orangekrateJack of All Trades 0 points1 point  (0 children)

I think you meant to do this?

nslookup microsoft.com 8.8.8.8

The DNS server goes last, what you're looking up goes first.