Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to do something I thought would be pretty simple.

Mapping local.mydomain.com to 192.168.0.1 using my registrar's DNS server.(namecheap.com)

I've added an A Record for local with value of 192.168.0.1

trying to lookup local.mydomain.com using websites like just-dnslookup.com returns the proper IP address. but trying to ping or nslookup in windows results in these errors.

Ping: Ping request could not find host local.mydomain.com. Please check the name and try again.

nsloojup No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for local.mydomain.com.

changing the ip address for the a record to a non-private ip (eg. 168.62.9.65) fixes the lookup issue.

I'm suspecting windows doesn't like the fact that a local ip is returned by the DNS server?

share|improve this question
add comment

1 Answer

up vote 4 down vote accepted

Indirect references to such addresses should be contained within the enterprise. Prominent examples of such references are DNS Resource Records and other information referring to internal private addresses. In particular, Internet service providers should take measures to prevent such leakage. -- RFC 1918

You are not supposed to be propogating DNS records with RFC 1918 addresses outside your enterprise. If you want to create an "internal" version of your DNS zone that contains internal addresses, that's fine (and that will work). But you are not supposed to use the Internet's DNS backbone to do it.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.