Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I just recently set up a DNS server and I'm having problems with it trying to resolve internal ip addresses. As of right now everything seems to be working ok except for when I try to ping a box or telnet to a router by the name it can't find it unless I type the domain along with it. For instance:
typing hostname.domain.net works fine however,
typing hostname results in nothing.
I had it setup where it would do it once before but the box got hosed and now I have to start from scratch and don't remember how I had it set up from before.
0.0.10.in-addr.arpa. IN SOA Boss.Saleen.net.
0.0.10.in-addr.arpa. IN NS dns.saleen.net.
220.127.116.11.in-addr.arpa. IN PTR saleen2611.
18.104.22.168.in-addr.arpa. IN PTR saleenwap.
22.214.171.124.in-addr.arpa. IN PTR saleen2950.
126.96.36.199.in-addr.arpa. IN PTR saleen1901.
188.8.131.52.in-addr.arpa. IN PTR saleen1902.
184.108.40.206.in-addr.arpa. IN PTR saleen2503.
220.127.116.11.in-addr.arpa. IN PTR dns.saleen.net.
10.0.0.10.in-addr.arpa. IN PTR shelby.
Saleen.net. IN SOA Boss.Saleen.net. (
Saleen.net. IN NS Boss.Saleen.net.
saleen2611.Saleen.net. IN A 10.0.0.1
saleenwap.Saleen.net. IN A 10.0.0.2
saleen2950.Saleen.net. IN A 10.0.0.3
saleen1901.Saleen.net. IN A 10.0.0.4
saleen1902.Saleen.net. IN A 10.0.0.5
saleen2503.Saleen.net. IN A 10.0.0.6
shelby.Saleen.net. IN A 10.0.0.10
boss.Saleen.net. IN A 10.0.0.11
10.0.0.1.Saleen.net. IN PTR saleen2611
// named.conf for Red Hat caching-nameserver
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
I think that this a client issue: you may need to specify a default domain on the client in order to use hostnames without a domain. On Linux this may be manually set in /etc/resolv.conf, but the default search domain probably ought to be issued by DHCP if the system uses it.
Try using nslookup to see what happens. If nslookup for a registered system on your network without a domain name result in NXDOMAIN I would double-check that the both the DNS server and the clients have the correct search domain set. Since a lookup by FQDN succeeds, DNS itself is probably operating correctly.
Although this isn't likely to be the issue, you probably ought to use lowercase for names of hosts and domains. Although DNS will cope, the fact that UNIX systems are case-sensitive means that names like Boss.Saleen.net may cause problems later. For example, I've had mail systems break because of issues with case-sensitivity.