Sponsored Content
Operating Systems Linux Red Hat Name resolution is only working from server side. Clients cannot resolve host names. Post 302728231 by admin_xor on Wednesday 7th of November 2012 01:38:46 PM
Old 11-07-2012
You do not have to re-install things.
You can check your config file syntax by named-checkconf, to check zone file confignamed-checkzone zonename

Check if the port 53 (both udp and tcp) is open in the iptables (if it's set to on) or any external firewall sitting between the client and server.

Check if both the server and the client are on the same subnet, if not, make sure that routing is taking place properly.
 

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
NAMED-CHECKZONE(8)						       BIND9							NAMED-CHECKZONE(8)

NAME
named-checkzone, named-compilezone - zone file validity checking or converting tool SYNOPSIS
named-checkzone [-d] [-h] [-j] [-q] [-v] [-c class] [-f format] [-F format] [-i mode] [-k mode] [-m mode] [-M mode] [-n mode] [-L serial] [-o filename] [-r mode] [-s style] [-S mode] [-t directory] [-T mode] [-w directory] [-D] [-W mode] {zonename} {filename} named-compilezone [-d] [-j] [-q] [-v] [-c class] [-C mode] [-f format] [-F format] [-i mode] [-k mode] [-m mode] [-n mode] [-L serial] [-r mode] [-s style] [-t directory] [-T mode] [-w directory] [-D] [-W mode] {-o filename} {zonename} {filename} DESCRIPTION
named-checkzone checks the syntax and integrity of a zone file. It performs the same checks as named does when loading a zone. This makes named-checkzone useful for checking zone files before configuring them into a name server. named-compilezone is similar to named-checkzone, but it always dumps the zone contents to a specified file in a specified format. Additionally, it applies stricter check levels by default, since the dump output will be used as an actual zone file loaded by named. When manually specified otherwise, the check levels must at least be as strict as those specified in the named configuration file. OPTIONS
-d Enable debugging. -h Print the usage summary and exit. -q Quiet mode - exit code only. -v Print the version of the named-checkzone program and exit. -j When loading the zone file read the journal if it exists. -c class Specify the class of the zone. If not specified, "IN" is assumed. -i mode Perform post-load zone integrity checks. Possible modes are "full" (default), "full-sibling", "local", "local-sibling" and "none". Mode "full" checks that MX records refer to A or AAAA record (both in-zone and out-of-zone hostnames). Mode "local" only checks MX records which refer to in-zone hostnames. Mode "full" checks that SRV records refer to A or AAAA record (both in-zone and out-of-zone hostnames). Mode "local" only checks SRV records which refer to in-zone hostnames. Mode "full" checks that delegation NS records refer to A or AAAA record (both in-zone and out-of-zone hostnames). It also checks that glue address records in the zone match those advertised by the child. Mode "local" only checks NS records which refer to in-zone hostnames or that some required glue exists, that is when the nameserver is in a child zone. Mode "full-sibling" and "local-sibling" disable sibling glue checks but are otherwise the same as "full" and "local" respectively. Mode "none" disables the checks. -f format Specify the format of the zone file. Possible formats are "text" (default) and "raw". -F format Specify the format of the output file specified. For named-checkzone, this does not cause any effects unless it dumps the zone contents. Possible formats are "text" (default) and "raw" or "raw=N", which store the zone in a binary format for rapid loading by named. "raw=N" specifies the format version of the raw zone file: if N is 0, the raw file can be read by any version of named; if N is 1, the file can be read by release 9.9.0 or higher. The default is 1. -k mode Perform "check-names" checks with the specified failure mode. Possible modes are "fail" (default for named-compilezone), "warn" (default for named-checkzone) and "ignore". -L serial When compiling a zone to 'raw' format, set the "source serial" value in the header to the specified serial number. (This is expected to be used primarily for testing purposes.) -m mode Specify whether MX records should be checked to see if they are addresses. Possible modes are "fail", "warn" (default) and "ignore". -M mode Check if a MX record refers to a CNAME. Possible modes are "fail", "warn" (default) and "ignore". -n mode Specify whether NS records should be checked to see if they are addresses. Possible modes are "fail" (default for named-compilezone), "warn" (default for named-checkzone) and "ignore". -o filename Write zone output to filename. If filename is - then write to standard out. This is mandatory for named-compilezone. -r mode Check for records that are treated as different by DNSSEC but are semantically equal in plain DNS. Possible modes are "fail", "warn" (default) and "ignore". -s style Specify the style of the dumped zone file. Possible styles are "full" (default) and "relative". The full format is most suitable for processing automatically by a separate script. On the other hand, the relative format is more human-readable and is thus suitable for editing by hand. For named-checkzone this does not cause any effects unless it dumps the zone contents. It also does not have any meaning if the output format is not text. -S mode Check if a SRV record refers to a CNAME. Possible modes are "fail", "warn" (default) and "ignore". -t directory Chroot to directory so that include directives in the configuration file are processed as if run by a similarly chrooted named. -T mode Check if Sender Policy Framework records (TXT and SPF) both exist or both don't exist. A warning is issued if they don't match. Possible modes are "warn" (default), "ignore". -w directory chdir to directory so that relative filenames in master file $INCLUDE directives work. This is similar to the directory clause in named.conf. -D Dump zone file in canonical format. This is always enabled for named-compilezone. -W mode Specify whether to check for non-terminal wildcards. Non-terminal wildcards are almost always the result of a failure to understand the wildcard matching algorithm (RFC 1034). Possible modes are "warn" (default) and "ignore". zonename The domain name of the zone being checked. filename The name of the zone file. RETURN VALUES
named-checkzone returns an exit status of 1 if errors were detected and 0 otherwise. SEE ALSO
named(8), named-checkconf(8), RFC 1035, BIND 9 Administrator Reference Manual. AUTHOR
Internet Systems Consortium COPYRIGHT
Copyright (C) 2004-2007, 2009-2011, 2013 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000-2002 Internet Software Consortium. BIND9 June 13, 2000 NAMED-CHECKZONE(8)
All times are GMT -4. The time now is 07:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy