Sponsored Content
Operating Systems Linux Red Hat Name resolution is only working from server side. Clients cannot resolve host names. Post 302729297 by dbadmin100 on Friday 9th of November 2012 12:06:45 PM
Old 11-09-2012
I had removed the bind packages by the time your message was posted. But this time I did not install the bind-chroot package and used the standard bind. However, I hit exactly the same issue. [can ping ip addresses in all directions but hostname ping only works from server]. So I checked the udp/tcp port 53 but did not find them in netstat -an. I issued the following commands as found in google and did /etc/init.d/iptables restart but no joy. So looks like this might be the issue why my clients cannot reach the dns server. Any ideas on how to open udp and tcp port 53 please (CentOS 5)?

Code:
iptables -A INPUT -p tcp -m tcp --sport 53 --dport 1024:65535 -m state --state ESTABLISHED -j ACCEPT
iptables -A INPUT -p udp -m udp --sport 53 --dport 1024:65535 -m state --state ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p tcp -m tcp --sport 1024:65535 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p udp -m udp --sport 1024:65535 --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT

 

10 More Discussions You Might Find Interesting

1. IP Networking

Cannot Resolve Host Name

I am running LexMark MarkNetPro-3 print servers on my AIX network. All of the sudden, none of my printers will print anymore. I am getting an error message on the console: Unable to resolve host name. This message comes up everytime a user submits a print job. Any Ideas? (1 Reply)
Discussion started by: Docboyeee
1 Replies

2. Shell Programming and Scripting

Server side scripting

I have my webpage hosted on one unix server, and using the command <!--#exec cmd="./nUsers.sh"--> it calls the appropriate script to tell me how many people are on the unix server at that time. I need to be able to find out how many users are on another unix server without logging in but using the... (1 Reply)
Discussion started by: paladyn_2002
1 Replies

3. UNIX for Advanced & Expert Users

host alias not working: host not found

Hello, I am working on HP-UX , and in the /etc/hosts file we have setup an alias: aa.bb.cc.dd devmach2.unix.org devmach2 devma2v The alias devma2v does not work. Error when pinging devma2v ping: unknown host devma2v For devmach2 the ping works fine , returning the correct IP... (4 Replies)
Discussion started by: FunnyCats
4 Replies

4. UNIX for Advanced & Expert Users

SUSE 9 and 10 NIS clients with RedHat 8.0 NIS server not working

We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave. We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation. However, no matter what i do, the SUSE machines will not talk to the NIS Servers. If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies

5. Linux

resolve one IP on DNS server

Hi! I have a dns server (bind) with 2 zones forward and reverse and i need to resolve one ip completely different. I have add to /etc/hosts and i can ping but i can't do nslookup. I've tried to add the dns server responsible to resolve that ip on /etc/resolv.conf without success. So how can i... (2 Replies)
Discussion started by: BufferExploder
2 Replies

6. Web Development

Cannot access Apache web server from Wan side, only Lan side.

I have installed WAMPSERVER 2.0 on my windows vista x64 system but still am having issues with getting the webserver to be seen outside my local network. It is working fine within my local network. Been through several setup tutorials so far, no dice still. For testing purposes I have... (1 Reply)
Discussion started by: davidmanvell
1 Replies

7. IP Networking

How to host apps for thin-clients for cheap on a home network?

Hello, I am planning to build a HP Proliant DL380 server w/ Debian. I would like to connect 6 or 8 thin clients (or zero-clients) to this server and host the applications for the thin clients. The thin-clients are all wireless LAN. All data created by users on the thin clients saved on the... (0 Replies)
Discussion started by: Marcus Aurelius
0 Replies

8. UNIX for Advanced & Expert Users

host file : same ip with different names

Dear Unix experts My application runs on Linux. The host file has the same ip address in two differnt lines but with different names. For example 10.114.45.14 prod.xyz.com prodx 10.114.45.14 prod-int.xyz.com prodx-int Could you please let me know if it is right? What is the... (2 Replies)
Discussion started by: nathan_nathan
2 Replies

9. Programming

Clients - Server ( UDP )

Hello, I have a question: I want to create a n client to one server connection. This is the client-server algorithm. Enybody help to make the changes? (0 Replies)
Discussion started by: MaHmur
0 Replies

10. Linux

My server can't resolve domains?

I am on a VPS that is pretty much unmanaged so it means im on my own. I did my best to configure it so i can host my own site for other people to see it online but seems like i have network problems because in the last days many of my users report they cant enter my site from my domain and... (7 Replies)
Discussion started by: supercain
7 Replies
NTPDC(1)						      General Commands Manual							  NTPDC(1)

NAME
ntpdc - special NTP query program SYNOPSIS
ntpdc [-ilnps] [-c command] [host] [...] DESCRIPTION
ntpdc is used to query the ntpd daemon about its current state and to request changes in that state. The program may be run either in interactive mode or controlled using command line arguments. Extensive state and statistics information is available through the ntpdc interface. In addition, nearly all the configuration options which can be specified at startup using ntpd's configuration file may also be specified at run time using ntpdc. If one or more request options are included on the command line when ntpdc is executed, each of the requests will be sent to the NTP servers running on each of the hosts given as command line arguments, or on localhost by default. If no request options are given, ntpdc will attempt to read commands from the standard input and execute these on the NTP server running on the first host given on the command line, again defaulting to localhost when no other host is specified. ntpdc will prompt for commands if the standard input is a terminal device. ntpdc uses NTP mode 7 packets to communicate with the NTP server, and hence can be used to query any compatible server on the network which permits it. Note that since NTP is a UDP protocol this communication will be somewhat unreliable, especially over large distances in terms of network topology. ntpdc makes no attempt to retransmit requests, and will time requests out if the remote host is not heard from within a suitable timeout time. The operation of ntpdc are specific to the particular implementation of the ntpd daemon and can be expected to work only with this and maybe some previous versions of the daemon. Requests from a remote ntpdc program which affect the state of the local server must be authen- ticated, which requires both the remote program and local server share a common key and key identifier. Note that in contexts where a host name is expected, a -4 qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a -6 qualifier forces DNS resolution to the IPv6 namespace. OPTIONS
Specifying a command line option other than -i or -n will cause the specified query (queries) to be sent to the indicated host(s) immedi- ately. Otherwise, ntpdc will attempt to read interactive format commands from the standard input. -4 Force DNS resolution of following host names on the command line to the IPv4 namespace. -6 Force DNS resolution of following host names on the command line to the IPv6 namespace. -c command The following argument is interpreted as an interactive format command and is added to the list of commands to be executed on the specified host(s). Multiple -c options may be given. -i Force ntpdc to operate in interactive mode. Prompts will be written to the standard output and commands read from the standard input. -l Obtain a list of peers which are known to the server(s). This switch is equivalent to -c listpeers. -n Output all host addresses in dotted-quad numeric format rather than converting to the canonical host names. -p Print a list of the peers known to the server as well as a summary of their state. This is equivalent to -c peers. -s Print a list of the peers known to the server as well as a summary of their state, but in a slightly different format than the -p switch. This is equivalent to -c dmpeers. SEE ALSO
/usr/share/doc/ntp-doc/html/ntpdc.html for the full documentation. Network Time Protocol October 7, 2006 NTPDC(1)
All times are GMT -4. The time now is 08:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy