Sponsored Content
Full Discussion: Bind 9.9.2 not working
Operating Systems Linux Red Hat Bind 9.9.2 not working Post 302754865 by rink on Friday 11th of January 2013 10:12:49 AM
Old 01-11-2013
Quote:
Originally Posted by thmnetwork
You can always increase the log level of bind, restart it, try a few queries and se if it prints anything more descriptive to /var/log/messages. More info on that process
Hello thmnetwork i also tried every main logging option and run named daemon with different debug level but nothing working.

I took one root dns server for testing
=> ping 198.41.0.4(root server) is working
=> dig -t A google.com @198.41.0.4 is working
=> named daemon is running

but not working local
dig -t A google.com @127.0.0.1 +trace (not working)
error no server could be reached

Now i think forwarders is the last option to use bind

Any help
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

bind version

How do I find out my current version of BIND? Dhall1973:D (1 Reply)
Discussion started by: dhall1973
1 Replies

2. UNIX for Advanced & Expert Users

Bind Problem

Hi all, I've 2 Debian Etch (4) box used as ns1 and ns2 with BIND9. My domain name is something like this: subdomain.domain.com And I've 2 authorized DNS servers for the subdomain. I set this line in both of ns1 and ns2 (I.e. in ns1.subdomain.domain.com and ns2.subdomain.domain.com): cw ... (1 Reply)
Discussion started by: mjdousti
1 Replies

3. Solaris

rpc bind not working

Hi all, Was hoping someone could shed some light on my problem, rpc bind is in maintenance mode on Solaris 10 and won't fire up. contents of the error log are: rpcbind failed with 1. bash-3.00# Because rpc-bind isn't working, it's stopping nfs and autofs from working too ... (6 Replies)
Discussion started by: callmebob
6 Replies

4. Red Hat

NFS - IP bind

Hello, Our production linux server have multiple network interface. Recently we installed and started NFS. Now the client server cannot mount to the server running NFS. Later it was discovered that the port being used for NFS is only bound to one IP address, which is not the IP address I... (0 Replies)
Discussion started by: hemangjani
0 Replies

5. Red Hat

BIND configuration

I have problems with a simple BIND configuration in CentOS. I have a static public IP 1.1.1.1 and I recently bought a domain name gigi.com. I just want that gigi.com points to 1.1.1.1 (Apache Web Server). This is how my named.conf file looks: options { directory "/var/named"; }; ... (0 Replies)
Discussion started by: pasadia
0 Replies

6. Red Hat

Split DNS not working with Bind-9.7

Hi All, Distros of machines : RHEL6 Bind Vesrion : Bind-9.7-3.2 I am trying to set up a test DNS for my home network. I have two rhel 6 machines A and B. Machine A has 2 NICs and is acting as a router also, one NIC is facing intranet and the otehr is facing intranet. On machine A i have... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies

7. Programming

bind source

here is the bind source file for the client.c in bind9 logs are written in var/log/file name in the form 02-Aug-2012 15:43:12.713 client 192.168.2.4#47512: query: 209.236.125.74.in-addr.arpa IN PTR + (192.168.2.4) i am in a subnet of 10 systems through 192.168.2.1..10 i want to write logs based... (2 Replies)
Discussion started by: balvinder87
2 Replies

8. UNIX for Dummies Questions & Answers

Can't bind to IP

When you get the message can't bind to ip already in use. is there a command to search to see everything that is using that IP? I've already check the host and hostname files (2 Replies)
Discussion started by: mchelle_99
2 Replies

9. UNIX for Advanced & Expert Users

Bind

Hi All I need to do bind of exiting filesystem to new storage allocated mount --bind /prod/OpenCSS /var/lib/test echo "/prod/OpenCSS /var/lib/pgsql bind bind 0 0" >> /etc/fstab will this command just work ? (2 Replies)
Discussion started by: anil529
2 Replies
named(1M)						  System Administration Commands						 named(1M)

NAME
named - Internet domain name server SYNOPSIS
named [-fgsv] [-c config-file] [-d debug-level] [-n #cpus] [-p port] [-t directory] [-u user] [-x cache-file] DESCRIPTION
The named utility is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC. For more information on the DNS, see RFCs 1033, 1034, and 1035. When invoked without arguments, named reads the default configuration file /etc/named.conf, reads any initial data, and listens for queries. OPTIONS
The following options are supported: -c config-file Use config-file as the configuration file instead of the default /etc/named.conf. To ensure that reloading the configura- tion file continues to work after the server has changed its working directory due to to a possible directory option in the configuration file, config-file should be an absolute pathname. -d debug-level Set the daemon's debug level to debug-level. Debugging traces from named become more verbose as the debug level increases. -f Run the server in the foreground (that is, do not daemonize). -g Run the server in the foreground and force all logging to stderr. -n #cpus Create #cpus worker threads to take advantage of multiple CPUs. If not specified, named will try to determine the number of CPUs present and create one thread per CPU. If it is unable to determine the number of CPUs, a single worker thread will be created. -p port Listen for queries on port port. If not specified, the default is port 53. -s Write memory usage statistics to stdout on exit. This option is mainly of interest to BIND 9 developers and might be removed or changed in a future release. -t directory Change the root directory using chroot(2) to directory after processing the command line arguments, but before reading the configuration file. This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance secu- rity on most systems; the way chroot() is defined allows a process with root privileges to escape a chroot jail. -u user Set the real user ID using setuid(2) to user after completing privileged operations, such as creating sockets that listen on privileged ports. On Linux, named uses the kernel's capability mechanism to drop all root privileges except the ability to use bind(3SOCKET) to bind to a privileged port and set process resource limits. Unfortunately, this means that the -u option works only when named is run on kernel 2.2.18 or later, or kernel 2.3.99-pre3 or later, since previous kernels did not allow privileges to be retained after setuid(). -v Report the version number and exit. -x cache-file Load data from cache-file into the cache of the default view. This option must not be used. It is of interest only to BIND 9 developers and might be removed or changed in a future release. SIGNALS
In routine operation, signals should not be used to control the nameserver; rndc(1M) should be used instead. SIGHUP Force a reload of the server. SIGINT, SIGTERM Shut down the server. The result of sending any other signals to the server is undefined. CONFIGURATION
The named configuration file is too complex to describe in detail here. A complete description is provided in the BIND 9 Administrator Ref- erence Manual. FILES
/etc/named.conf default configuration file /var/run/named.pid default process-ID file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWbind9 | |Interface Stability |External | +-----------------------------+-----------------------------+ SEE ALSO
rndc(1M), chroot(2), setuid(2), bind(3SOCKET), attributes(5) RFC 1033, RFC 1034, RFC 1035 BIND 9 Administrator Reference Manual NOTES
Source for BIND9 is available in the SUNWbind9S package. SunOS 5.10 15 Dec 2004 named(1M)
All times are GMT -4. The time now is 08:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy