DNS resolution problem, Can not resolve from intranet
Hello I have such problem, I have IP on win 2008, 111.111.111.111 sharing it to 192.168.0.x net I have domain name on 111.111.111.111 but computers from lan cant resolve it, as dns sends them to 111.111.111.111 If I put 192.168.0.1 on dns resolution, computers outside the lan resolve domain to 192... and of course could not connect So, please let me know what is solution, how to make lan computers go to 192.168..0.1 and all others on 111.111.111.111 ? No AD, just DNS, IIS, RAS,
August 17th, 2010 11:45pm

Hello, you could use different comptuer names for the same machine in dns. use a internal dns name for the 192 and external dns name for dns request coming from computers out side your lan. would this possible in your situation? regards
Free Windows Admin Tool Kit Click here and download it now
August 17th, 2010 11:57pm

It is difficult to understand what you are describing. Based on the last statement, "So, please let me know what is solution, how to make lan computers go to 192.168..0.1 and all others on 111.111.111.111" and what I can gather from the rest of the post... I think this is what you are asking: What is the solution for computers to access a server using two NICs IPs (192.168.0.1 & 111.111.111.111) so that internal LAN computers access it by 192.168.0.1 and Internet computers accessing it by 111.111.111.111? If that is what you are indeed asking, you need to have a split-DNS infrastructure. What I mean by that is that you need an Internal DNS server hosting the domain which includes a host record for this server pointing to the IP of 192.168.0.1, and you also need to have an External DNS server hosting the same domain with a record for this server pointing to the IP of 111.111.111.111. Your internal computers will configure their TCP/IP settings to point the DNS client to the internal DNS server, while everyone else on Internet Land will by default resolve the host name using the External DNS server. I hope that this is what you were asking about as this was quite a bit of typing.... Visit: anITKB.com, an IT Knowledge Base.
August 18th, 2010 4:32am

Thank you very much for answers JM Yes, I mean exactly that! two dns servers are only solution? No option to divide lan clients and outside clients to get different name resolution for same host?
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2010 12:52pm

Hello, Did you try to use Forwarders or conditional forwarders? Regards,
August 19th, 2010 1:08pm

Hi , Please remember that if you are planning this on a DC ,its unrecommended setup. I have seen customers configuring server with dual NIC and configuring DNS , is this what your looking at ?
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2010 2:21pm

Hello Donkosta, I am glad that I was able to understand your question and provide you with an answer. In regards to your question, "two dns servers are only solution?", based on the scenario you described, I would say so. DNS provides centralization and scalability in regards to host name resolution. Another option that is avaiable to you is to use the HOSTS file for your internal computers. I would only recommend this option if you only have a handful of computers to manage. The HOSTS file is checked by Windows prior to using a DNS server. Therefore, you could add an entry in the HOSTS file on each computer. For example, an entry might look like this: hostName.domain.com 192.168.0.1. The HOSTS file is located on Windows systesm here: %systemroot%\system32\drivers\etc\ The HOSTS file is updated via a text editor such as NOTEPAD. Visit: anITKB.com, an IT Knowledge Base.
August 19th, 2010 4:18pm

yes, thats it I have 2 nics and sharing internet through them
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 5:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics