HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Testing DNS fails
Operating System - Linux
1828663
Members
1417
Online
109984
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2005 04:50 AM
09-02-2005 04:50 AM
I have a single server and want to configure the DNS and Apache on it. I am using redhat Linux 9.MY server has no connection to the internet. I am using a Class C address of 192.168.45.1 on my network card. I have also configure the /etc/namded.conf with the appropiates settings.I also went to the /var/named and created my zone record for both forward and reverse zone. I also put an entry for the 192.168.45.1. in my zone record. My named service is running but when i run chkconfig --list named, i see named service off at all the run level.i also ran the ps ax |grep named command. I see the named process running. When i do the netstat -ant |grep 53
i see my current ip address listening to port 53.but when i try testing the dns with dig + ip address i get an error saying connection timed out no server found.Friend what is the problem. I need ur help and Advice. I also put the same ip address as the DNS for it self.
i see my current ip address listening to port 53.but when i try testing the dns with dig + ip address i get an error saying connection timed out no server found.Friend what is the problem. I need ur help and Advice. I also put the same ip address as the DNS for it self.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2005 05:00 AM
09-02-2005 05:00 AM
Solution
1. chkconfig named on
2. use dig www.yahoo.com @127.0.0.1 to get what You want
3. look at /etc/resolv.conf - does it contain 'nameserver 127.0.0.1' in the first line? (You might want to not change that before the tests turn out ok)
4. are there any error messages in /var/log/daemon.log or /var/log/messages (or whereever messages go in redhat, I don't recall at the moment)
5. please try to make Your text a slight bit more readable next time :)
2. use dig www.yahoo.com @127.0.0.1 to get what You want
3. look at /etc/resolv.conf - does it contain 'nameserver 127.0.0.1' in the first line? (You might want to not change that before the tests turn out ok)
4. are there any error messages in /var/log/daemon.log or /var/log/messages (or whereever messages go in redhat, I don't recall at the moment)
5. please try to make Your text a slight bit more readable next time :)
yesterday I stood at the edge. Today I'm one step ahead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2005 07:25 AM
09-02-2005 07:25 AM
Re: Testing DNS fails
As said above, you should use the @ character to specify the server to connect.
dig @server fqdn
You should verify that the resolv.conf is correct, should have:
nameserver 127.0.0.1
And finally, if you want to test the reverse resolution (IP to HOST), you must use the -x option of the dig command.
dig @server fqdn
You should verify that the resolv.conf is correct, should have:
nameserver 127.0.0.1
And finally, if you want to test the reverse resolution (IP to HOST), you must use the -x option of the dig command.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP