Sponsored Content
Full Discussion: BIND problem in Fedora Core
Operating Systems Linux BIND problem in Fedora Core Post 302224763 by narasimhulu on Thursday 14th of August 2008 01:53:46 AM
Old 08-14-2008
Solved

Hello all,

I have solved the problem by removing 2 lines from /etc/named.caching-nameserver.conf file. Now i can able to resolve the host names from the client machines.

match-clients { localhost; };
match-destinations { localhost; };

Thanks a lot,
Narasu
 

10 More Discussions You Might Find Interesting

1. Linux

Using Fedora Core 2

I've been using FC2, but my sound card doesn't work I'm new with linux systems.. but there says that needs to recompile kernel how can i do it with a kernel 2.6.5 i386 ? by the way,. my sound card chipset is an ESS 1869F, with a compaq deskpro Smal Form Factor. but i have not found a... (4 Replies)
Discussion started by: Quake
4 Replies

2. Linux

being probed Fedora core 2

Lucky me...someone's trying to hack into my mythtv box through ssh. Can I make a policy or something similar to refuse connections from a specific IP after a certain amount of failed logins? attached is some of the output from /var/log/messages (2 Replies)
Discussion started by: dangral
2 Replies

3. Linux

Trying to install Fedora Core 3...

Hiya all, Hope you can help. I keep getting the same Error message when I try to install. I have tried several different Diskettes. And I finally ordered CDs from "FASTDISCs". The install "disc Checks" passed fine on these. The error: "The package usbitils-0.11.6.1 cannot be opened. ... (8 Replies)
Discussion started by: marty 600
8 Replies

4. Linux

fedora core 2 selinux problem

in fedora core 2 with enforcing mode in selinux , why even as a root OS doesnt give permission to create any directory or file in /home ? (1 Reply)
Discussion started by: the.last.soul
1 Replies

5. Linux

Help with OpenGL in Fedora Core 4.

I'm pretty much new to this Linux stuff, I installed FC4 the other night to try it out. I'm having a slight problem when launching Quake 3, it's giving me the error GLimp_Init() - could not load OpenGL subsystem I've updated my video drivers to the latest version and went through fglrxconfig,... (3 Replies)
Discussion started by: Filth Pig
3 Replies

6. UNIX for Dummies Questions & Answers

Installing Fedora Core 4

Hello, I am about to install Fedora on a partition on my hard drive. I got the CD from a magazine and it isnt a LiveCD so the magazine says "fedora core installer isn't a LiveCD, so it will merrily destroy your primary partition when you install on your machine", now I'm guessing the primary... (1 Reply)
Discussion started by: ArkNia
1 Replies

7. Linux

NFS problem in Fedora Core 4

Hi all, I'm experiencing a problem with Fedora Core 4, by which I don't know how to export a directory exclusively in NFSv3. I have two raid arrays "/dev/md0" and "/dev/md1" both to be visible to SGI machines via NFSv3... My situation is that Fedora runs NFSv4 and that causes problems with the... (0 Replies)
Discussion started by: spaceace13666
0 Replies

8. Linux

fedora core 6 problem

hi all i am currently using fedora core 3 . i downloaded the iso image of fedora core 6 but after installing the fedora core 6 . while starting linux it gives a error saying init is been killed . wht is happened? thank u (3 Replies)
Discussion started by: nageshrk
3 Replies

9. Linux

mysql in fedora core 4

hi i dont know much about linux but my boss gave me a job to backup all the mysql database and tables from fedora core4 running as web/database server. i can enter in fedora using remote desktop from my laptop but after that i am unable to do anything. if any one can help me in finding mysql and... (3 Replies)
Discussion started by: obstinate
3 Replies

10. Red Hat

Problem to bind to local ports on Fedora 13

A problem with binding to local ports (22,23,80) in Fedora 13. Ports look not used. sshd, webserver is not running. I am using java remote connection manager. It is working fine with IE or Firefox in Windows with any user account. With Fedora 13, it starts via Firefox with not root account and... (0 Replies)
Discussion started by: gogogo
0 Replies
resolver(5)						      BSD File Formats Manual						       resolver(5)

NAME
resolver -- resolver configuration file format DESCRIPTION
The resolver is a set of routines in the C library resolv(3) that provide access to the Internet Domain Name System (DNS). A resolver con- figuration file contains information used to specify parameters for a DNS resolver client. The file contains a list of keywords with values that provide various types of resolver information. Mac OS X supports a DNS search strategy that may involve multiple DNS resolver clients. See the SEARCH STRATEGY section below for an over- view of multi-client DNS search. Each DNS client is configured using the contents of a single configuration file of the format described below, or from a property list sup- plied from some other system configuration database. Note that the /etc/resolv.conf file, which contains configuration for the default (or "primary") DNS resolver client, is maintained automatically by Mac OS X and should not be edited manually. Changes to the DNS configuration should be made by using the Network Preferences panel. The different configuration options are given below. nameserver Internet address (in dot notation for IPv4 or in colon notation for IPv6) of a name server that the resolver should query. The address may optionally have a trailing dot followed by a port number. For example, 10.0.0.17.55 specifies that the nameserver at 10.0.0.17 uses port 55. Up to MAXNS (currently 3) name servers may be listed, one per keyword. If there are multiple servers, the resolver library queries them in the order listed. The algorithm used is to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the name servers until a maximum number of retries are made. port IP port number to be used for this resolver. The default port is 53. The port number for an individual nameserver may be specified as part of the nameserver address (see nameserver above) to override the default or the port number specified as a value for this keyword. domain Domain name associated with this resolver configuration. This option is normally not required by the Mac OS X DNS search system when the resolver configuration is read from a file in the /etc/resolver directory. In that case the file name is used as the domain name. However, domain must be provided when there are multiple resolver clients for the same domain name, since multiple files may not exist having the same name. See the SEARCH STRATEGY section for more details. search Search list for host-name lookup. This parameter is only used by the "Super" DNS resolver, which manages the DNS search strategy amongst multiple DNS resolver clients. Unqualified queries will be attempted using each component of the search list in turn until a match is found. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. search_order Only required for those clients that share a domain name with other clients. Queries will be sent to these clients in order by ascending search_order value. For example, this allows two clients for the ".local" domain, which is used by Apple's multicast DNS, but which may also be used at some sites as private DNS domain name. sortlist Sortlist allows addresses returned by gethostbyname to be sorted. A sortlist is specified by IP address netmask pairs. The netmask is optional and defaults to the natural netmask of the net. The IP address and optional network pairs are separated by slashes. Up to 10 pairs may be specified. For example: sortlist 130.155.160.0/255.255.240.0 130.155.0.0 timeout Specifies the total amount of time allowed for a name resolution. This time interval is divided by the number of nameservers and the number of retries allowed for each nameserver. options Options allows certain internal resolver variables to be modified. The syntax is: options option ... where option is one of the following: debug sets RES_DEBUG in the resolver options. timeout:n sets the per-retry timeout for resolver queries. The total timeout allowed for a query depends on the number of retries and the number of nameservers. This value is ignored if a total timeout is specified using the timeout keyword (see above). ndots:n Sets a threshold for the number of dots which must appear in a name given to res_query (see resolver(3)) before an initial absolute query will be made. The default for n is ``1'', meaning that if there are any dots in a name, the name will be tried first as an absolute name before any search list elements are appended to it. The keyword and value must appear on a single line, and the keyword must start the line. The value follows the keyword, separated by white space. SEARCH STRATEGY
Mac OS X uses a DNS search strategy that supports multiple DNS client configurations. Each DNS client has its own set of nameserver addresses and its own set of operational parameters. Each client can perform DNS queries and searches independent of other clients. Each client has a symbolic name which is of the same format as a domain name, e.g. "apple.com". A special meta-client, known as the "Super" DNS client acts as a router for DNS queries. The Super client chooses among all available clients by finding a best match between the domain name given in a query and the names of all known clients. Queries for qualified names are sent using a client configuration that best matches the domain name given in the query. For example, if there is a client named "apple.com", a search for "www.apple.com" would use the resolver configuration specified for that client. The match- ing algorithm chooses the client with the maximum number of matching domain components. For example, if there are clients named "a.b.c", and "b.c", a search for "x.a.b.c" would use the "a.b.c" resolver configuration, while a search for "x.y.b.c" would use the "b.c" client. If there are no matches, the configuration settings in the default client, generally corresponding to the /etc/resolv.conf file or to the "pri- mary" DNS configuration on the system are used for the query. If multiple clients are available for the same domain name, the clients ordered according to a search_order value (see above). Queries are sent to these resolvers in sequence by ascending value of search_order. The configuration for a particular client may be read from a file having the format described in this man page. These are at present located by the system in the /etc/resolv.conf file and in the files found in the /etc/resolver directory. However, client configurations are not limited to file storage. The implementation of the DNS multi-client search strategy may also locate client configuratins in other data sources, such as the System Configuration Database. Users of the DNS system should make no assumptions about the source of the configuration data. FILES
/etc/resolv.conf, /etc/resolver/* SEE ALSO
gethostbyname(2), getaddrinfo(3), resolver(3) Mac OS X June 6, 2003 Mac OS X
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy