Sponsored Content
Full Discussion: Linux DNS issue
Operating Systems Linux Red Hat Linux DNS issue Post 302501865 by autoconfig on Saturday 5th of March 2011 08:29:19 AM
Old 03-05-2011
Linux DNS issue

Hi , I have configured OEL 5.3 server on VMware server,installation went fine, however when i am checking host using configured /etc/hosts i am getting following error let me know where it went wrong .

I had disabled firewall options and SELLinux.
Code:
root@oen11g ~]# host oen11g.grid.com 
;; connection timed out; no servers could be reached

here is /etc/hosts
Code:
[root@oen11g ~]# cat /etc/hosts 
# Do not remove the following line, or various programs 
# that require network functionality will fail. 
127.0.0.1 localhost.localdomain localhost 
10.103.10.125 ; oen11g.grid.com oen11g

I am able to ping
Code:
[root@oen11g ~]# ping 10.103.10.125 
PING 10.103.10.125 (10.103.10.125) 56(84) bytes of data. 
64 bytes from 10.103.10.125: icmp_seq=1 ttl=64 time=1.53 ms 
64 bytes from 10.103.10.125: icmp_seq=2 ttl=64 time=0.339 ms 

--- 10.103.10.125 ping statistics --- 
2 packets transmitted, 2 received, 0% packet loss, time 1001ms 
rtt min/avg/max/mdev = 0.339/0.936/1.533/0.597 ms 

[root@oen11g ~]# ping oen11g.grid.com 
PING oen11g.grid.com (10.103.10.125) 56(84) bytes of data. 
64 bytes from oen11g.grid.com (10.103.10.125): icmp_seq=1 ttl=64 time=0.036 ms 
64 bytes from oen11g.grid.com (10.103.10.125): icmp_seq=2 ttl=64 time=0.242 ms 
64 bytes from oen11g.grid.com (10.103.10.125): icmp_seq=3 ttl=64 time=0.234 ms 

--- oen11g.grid.com ping statistics --- 
3 packets transmitted, 3 received, 0% packet loss, time 2001ms 
rtt min/avg/max/mdev = 0.036/0.170/0.242/0.096 ms 

[[root@oen11g ~]# traceroute 10.103.10.125 
traceroute to 10.103.10.125 (10.103.10.125), 30 hops max, 40 byte packets 
1 oen11g.grid.com (10.103.10.125) 0.572 ms 0.026 ms 0.021 ms 

[root@oen11g ~]# dig +trace 10.103.10.125 

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> +trace 10.103.10.125 
;; global options: printcmd 
;; connection timed out; no servers could be reached 
[root@oen11g ~]#


Last edited by Scott; 03-05-2011 at 09:45 AM.. Reason: Please use code tags.
 

10 More Discussions You Might Find Interesting

1. IP Networking

DNS issue.

Hi, We use linux as a DNS server for our local network. ( linuxnol.nollekens.be ) We can ping this machine on all our XP clients like this: C:\>ping linuxnol Until yesterday it was on our XP clients enough to type "ping ibm250" ( our 2de unix server, an AIX ). But after a shutdown of this... (1 Reply)
Discussion started by: progressdll
1 Replies

2. UNIX for Advanced & Expert Users

linux firewall / dns issue

I have set up a linux (red hat 9) box as my main internet router. I am also running a DNS server on it. What are the rules i have to implement to allow DNS queries through the firewall from outside so that the outside world can see my domains? (1 Reply)
Discussion started by: frankkahle
1 Replies

3. Solaris

t2000 DNS issue

I have an issue with DNS on a solaris t2000 When I set up the zones there was an issue with the /etc/resolv.conf, I had made a typo in my DNS server. I only noticed this after creating my new zones. I have corrected this in the global zone and I am now able to ping and nslookup inthe... (2 Replies)
Discussion started by: james dewitt
2 Replies

4. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

5. Red Hat

DNS issue in Redhat 9

Hi all m newbie in linux and trying to setup my internal DNS server for local network.After messing with DNS for hours i am posting this. i have configured /etc/resolve.conf, hostname with domain name in /etc/sysconfig/network file,/etc/hosts file with local host entry and zone file... (1 Reply)
Discussion started by: Vaibhav.T
1 Replies

6. Red Hat

Issue in DNS set up

:wall:I am a beginer in Linux admin. I have build new DNS setting in my system. Please find the below procedure what I followed to build DNS. but at last when I fired nslookup command, its getting error. I am using RHEL5 OS. Please help me to resolve this below issue.. Advance thanks for... (1 Reply)
Discussion started by: pradipta_pks
1 Replies

7. Red Hat

dns update issue

i have redhat service as public dns i have added new entry but when i reload the named service i got this error in log the working directory is not writable (1 Reply)
Discussion started by: leganti
1 Replies

8. Red Hat

DNS Resolution Issue

Hello, Having issue resolving DNS using the IP address. Using the server Name it resolves fine. Was wondering if there is any configuration issue. # nslookup xxxxxxxx01 Server: Primary DNS IP Address: Primary DNS IP#53 Name: xxxxxxxx01.local domain Address: x.y.z.123 # nslookup... (1 Reply)
Discussion started by: ikn3
1 Replies

9. HP-UX

HP-UX DNS issue

Hi All, I'm having some problems with our HP-UX environment. I'm running Oracle EBS on a HP-UX system, and whenever my primary dns server goes down some of my clients can no longer connect. Everything on my windows side continues to work, and clients can reach the internet and other services... (6 Replies)
Discussion started by: agonza07
6 Replies

10. Linux

DNS Response Issue

Hi, I have a Windows based Domain (abc.com)servers like: 172.30.1.246 172.30.1.247 172.30.3.246 172.30.3.247 On all my Linux servers (/etc/resolv.conf) have a following DNS servers entries: nameserver 172.30.3.246 nameserver 172.30.3.247 But when i ping my Domain (abc.com), it... (5 Replies)
Discussion started by: refra
5 Replies
network-test(1) 						  ifupdown-extra						   network-test(1)

NAME
network-test - check the network and test if everything is fine SYNOPSIS
network-test DESCRIPTION
The network-test program will test your system's network configuration using basic tests and providing both information (INFO), warnings (WARN) and possible errors (ERR) based on the results of these tests. It will check and report on: * Status of the network interfaces of the system including: link status, IP addressing and number of transmitted packets and error rates. * Accessibility to configured routes to external networks, including the default network route, checking the routers configured to give access to the network * Proper host resolution, testing DNS resolution against a known host. * Proper network connectivity, testing reachability of remote hosts using ICMP and simulating a web connections to a remote web server (the web server used for the tests can be configured through the environment, see below) The program does not need special privileges to run as it does not do any system change. However, the behaviour of the program when running as an unprivileged user is not the same as running as system administrator (i.e. root). If the program is run as system administrator it will try to run some tools that are only available to it to speed up some of the tests. The program relies on the use of ip, netstat, ifconfig, arp and (when running as root) ethtool or mii-tool, to obtain information about the system's networking configuration (status of available interfaces and configured network routes). It also uses ping, host and nc (netcat) to do tests of the network connectivity and ensure that the host can connect to the Internet. ENVIRONMENT
The program will, by default, check www.debian.org and its associated web server. If you want to use a different check host you can setup the environment as follows: CHECK_HOST The name of a host to use when testing DNS resolution. CHECK_IP_ADRESS The IP address of the host defined in CHECK_HOST CHECK_WEB_HOST The web server to use for testing purposes when testing network connectivity. CHECK_WEB_PORT The web server port of server CHECK_WEB_HOST that will be used for testing. EXIT STATUS
The program will exit with error (1) if any of the network checks fail. BUGS
This program does not have super cow powers so it is unable to fix the errors by itself. It is also unable to detect if the network is failing due to a local firewall policy been in place so make sure you check your system logs with dmesg (1) to detect if some of the active tests are being dropped due to your local firewall. Other known issues that might make the program not work reliable are: * IPv6: The program does not yet explicitly handle IPv6 only hosts, some of the tests might be biased towards IPv4 and might fail in IPv6 environments. * Proxies: The program does not check network connectivity for hosts that connect through the Internet using a proxy gateway for services. The program might report issues in hosts using proxies even when these might connect to the Internet properly through proxied services. * Firewall environments: some of the tests rely on direct connectivity to external hosts, which are tested using ICMP queries (through the use of ping. These tests might fail in hosts installed in networking environments with firewalls that block outbound ICMP communication. SEE ALSO
ip (8), netstat (8), ifconfig (8), ethtool (8), mii-tool (8), ping (8), nc (1) and host (1). AUTHOR
network-test was written by Javier Fernandez-Sanguino for the Debian GNU/Linux distribution. COPYRIGHT AND LICENCE
Copyright (C) 2005-2011 Javier Fernandez-Sanguino <jfs@debian.org>. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. On Debian systems, a copy of the GNU General Public License may be found in /usr/share/common-licenses/GPL. ifupdown-extra August 23 2011 network-test(1)
All times are GMT -4. The time now is 03:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy