/build/static/layout/Breadcrumb_cap_w.png

Strange DNS Issue

Hi All,

I have a problem and solution, but need help understanding the cause. I have a laptop which is hardwired into our network with the wireless turned off. I set the static IP settings as follows

IP: 192.168.0.100
Mask: 255.255.0.0
Gateway: 192.168.0.36
DNS: 192.168.0.11, 192.168.1.3

I am trying to contact device horstj-7 (192.168.1.78). The device itself has the same gateway and DNS, but a mask of 255.255.240.0.

I can ping 192.168.1.78 with now problems. I can even do a ping /a and it returns the correct hostname. However, pinging horstj-7 returns "Ping request could not find host horstj-7..."

Changing the mask to the 240 subnet allows me to ping the hostname with no problems. Being curious, I changed to the 254 subnet. This should still work as my device is in the 0 range and the target is a 1. However, I can ping the IP with no problem, but not the hostname. Back to the 240 subnet and everything works fine.

I duplicated this same problem with another laptop. I noticed that there was no DNS entry in either DC for horstj-7. I added a Host (A) record, waited a few minutes, and did a force update on the laptop. It now works correctly regardless of the subnet.

This was obviously a DNS issue, but what could possibly cause the behavior where everything is fine if you are on ONE specific subnet mask? I would have thought that a DNS problem would be prevalent regardless of the mask.



0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ