Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

DNS Client fails to connect to DNS Server and unable to resolve host headers

$
0
0

Hi,

Host Machine Config : Windows 8 - Pro with Hyper-V, 12 GB RAM

1) Created an Internal Virtual Network, via Virtual Switch Manager. Once the Virtual Adapter is created I've doneICS (Internet Connection Sharing) with my WIFI Adapter and i get 192.168.137.1 as IP

2) Created two Windows 2012 Machines 

  • 1st host AD CS and DNS
  • 2nd host SharePoint 2013

3) Configured the same Internal network adapter with above both the machines and given static IP to both

Example:

DC Machine

IPv4 : 192.168.137.2

Subnet: 255.255.255.0

Default Gateway : 192.168.137.1

Primary DNS Server: 192.168.137.1

SP2013 Machine

IPv4 : 192.168.137.3

Subnet: 255.255.255.0

Default Gateway : 192.168.137.1

Primary DNS Server: 192.168.137.2

Well with this both my machine is on same network and has got internet access.

Created multiple A Records on my DNS Server (192.168.137.2). 

the problem is sometime, my SP2013 Machine doesn't really understands the host header so if i try to ping and see

e.g. ping demo.mydomain.local

it returns error : Ping request could not find host demo.mydomain.local. Please check the name and try again.

the workaround i followed

1. ipconfig /flushdns --> had to do 10-15 times, sometime it works and sometime not.

2. reset DNS Client Service -> This works all the time

What is going wrong !!! i'm not a expert IT infra guy so i'm not getting what's wrong


Thanks
Akhilesh Nirapure


Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>