in my /etc/resolv.conf i have
nameserver 127.0.0.1
and i have bind 9.3.4 running. The DNS server is working properly for any valid domain name out there today.
The issue i am having is if i try to ping an invalid domain like thisisobviouslyaninvaliddo
PING c18-ss-1-lb.cnet.com (216.239.122.33) 56(84) bytes of data.
64 bytes from c18-ss-1-lb.cnet.com (216.239.122.33): icmp_seq=1 ttl=241 time=43.8 ms
This response comes back for any and all invalid domains. My question is, how do i get my dnsserver to stop this? I don't want an IP address to come back to an invalid domain.
If you need more information, please let me know.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
FYI... com.com is a valid domain owned by CNET. This domain have wildcast record for *.com.com point to the hostname in your question, c18-ss-1-lb.cnet.com.
In my wild guess, what happened to you was that the system added .com to thisisobviouslyaninvaliddo
hnminh,
my /etc/resolv.conf only has 1 line in it.
nameserver 127.0.0.1
Should i add a "search" field to the file? Where can i find documentation on this?
Also, im not sure what config files you need for me to show you, i don't mind posting them... I'd really like to fix this issue so it makes items easier for me to troubleshoot.
Also, Thank you for replying to my question! :)
icullins,
searchs parameter in resolv.conf is used to auto append a domain into a hostname whenever this hostname could not be resolved by the DNS.
For example, if you have searchs as in attached code snippet, whenever you ping a host, say server1, the server will add the domain in searchs and try to ping server1.yourdmain.com instead. You can try add this line:
searchs localdomain
to ensure localdomain will always be appened to unknown host and hence would never be reosolved.
Business Accounts
Answer for Membership
by: hnminhPosted on 2009-03-18 at 02:57:51ID: 23916856
Are you using forwarding or employ root servers directly? If it is forwarding, the root cause could be from your ISP (upstream) DNS setting. In this case, you can try to use hint zone and remove forwarder setting.
Out-of-the-box caching-nameserver install won't have this happen. You might need to public your current config for futher discussion.