DNS not resolving to new machines on network after increasing DHCP pool size

ZylawyStephen — Mon, 11 Mar 2019 23:42:48 GMT

Hello,

I am having a very strange issue with connecting new machines to reach the internet.

We have a ASA 5505 which the previous tech configured the DHCP pool to 192.168.1.60 - 192.168.1.110

We ended up reaching our limit which I changed it to: 192.168.1.60 - 192.168.187

Then next day when I arrived to work, our DC was hung from windows updates. Once we got everything back up, every computer currently on the network can reach the internet/VPN tunnels etc. So (continuing with my day) I created a new server in a VM (Hyper-V)

I can ping everything internally (even the router) 192.168.1.1, but I cannot resolve DNS. I have configured a static IP, tried Dynamic IP.

I have looked for any ACL indicating to block outside the range of the old DHCP pool but no luck.

On my local maching I can ping the DNS addresses, but just not on the new server.

Can anyone point me in the right direction to where to look for this issue?

DNS not resolving to new machines on network after increasing DH

ZylawyStephen — Thu, 16 Aug 2012 14:09:54 GMT

I ended up figuring out what the issue was.

Since it was in a Hyper-V VM. the hosting server had to be updated to SP1.

Once completed, and rebooted. The VM in question got an IP address.

topic DNS not resolving to new machines on network after increasing DHCP pool size in Network Security

DNS not resolving to new machines on network after increasing DHCP pool size

DNS not resolving to new machines on network after increasing DH