Sponsored Content
Special Forums IP Networking HOWTO: Linux multihomed dns client - reverse lookup Post 302549092 by scheruga on Sunday 21st of August 2011 11:05:18 AM
Old 08-21-2011
HOWTO: Linux multihomed dns client - reverse lookup

The following thread is closed: 133552-howto-linux-multihomed-dns-client (Sorry I am not allowed to post URLs)

Therefore I write this append in an own thread.

The HOWTO in the referenced thread helped me a lot and I only want to append how to make reverse lookup working for a local zone:

One had to add the following lines:

Code:
zone "1.1.10.in-addr.arpa" {  // the reversed cluster of your local network
        type forward;
        forwarders {
                w.x.y.z; // your private name server
        };
};

 

10 More Discussions You Might Find Interesting

1. IP Networking

reverse lookup again

our server (solaris, bind v 8.1.2) is suppose to be the authoritive or the master and our isp's server is suppose be the secondary. i've created a reverse lookup zone file and added an entry for it in my named.conf file. i've restarted the dns daemon and i don't have any errors in... (1 Reply)
Discussion started by: Westy564
1 Replies

2. IP Networking

Reverse lookup

Help having problems accesing various sites that require me to be a registered .gov domain. My IP is a registered as an .gov but my nameserver record has changed on my DNS configurartion(I don't know why) from something.gov to somethingelse.gov. Same IP, though. When a reverse lookup is... (1 Reply)
Discussion started by: jpalmer320
1 Replies

3. Programming

Multihomed Client

Hi, I am writing a socket program at the moment that uses both of the clients network interfaces. The program tries to create two socket connections to the server over a LAN connection and a GPRS connection. I have tried to update the routing table using the route command but that proved... (0 Replies)
Discussion started by: mhynes
0 Replies

4. IP Networking

Multihomed DNS Clients?

I'm not sure it that's the right term for what I'm asking about, but it's the best I could come up with. Here is my situation... I'm setting up a network using OpenVPN. The clients I'm setting up will need to be able to access their own DNS servers (to resolve internal names at their location)... (4 Replies)
Discussion started by: deckard
4 Replies

5. UNIX for Advanced & Expert Users

Clueless about how to lookup and reverse lookup IP addresses under a file!!.pls help

Write a quick shell snippet to find all of the IPV4 IP addresses in any and all of the files under /var/lib/output/*, ignoring whatever else may be in those files. Perform a reverse lookup on each, and format the output neatly, like "IP=192.168.0.1, ... (0 Replies)
Discussion started by: choco4202002
0 Replies

6. Shell Programming and Scripting

Reverse lookup

hey guys, can anybody help me out here on the following: grep '^\{1,3\}\.\{1,3\}\.\{1,3\}\.\{1,3\}$' ravi.txt mary.txt lisa.txt https://www.unix.com/images/misc/progress.gif i.e what i did was found ip addreses from different files and then i want... (1 Reply)
Discussion started by: ravis83
1 Replies

7. UNIX for Advanced & Expert Users

[DNS] Reverse Lookup for 2 IP Addresses

Originally I had the server at home and on Comcast so I used dyndns.org for DNS. Once the server got a bit more popular, I leased a server at a colo facility. They set up the server name in their DNS so I didn't really have any reason to manage my own DNS. DynDNS was managing the domains and I... (7 Replies)
Discussion started by: BOFH
7 Replies

8. IP Networking

HOWTO: Linux multihomed dns client

The Linux resolver queries all nameservers in the order they are listed in /etc/resolver.conf. If a nameserver times out, it advances on to the following nameserver. But, if a nameserver returns "not found" (NXDOMAIN) it stops. This behaviour is problematic when you need to resolve names from... (0 Replies)
Discussion started by: colemar
0 Replies

9. Shell Programming and Scripting

Reverse lookup and sum also

Hi, I have log file name that shows the view name and some SQL statement time stamp. I want to summarize the SQL time with view. Here is the simple example Here the seqence is first it prints EventContext and all the SQL statement time and again EventContext. Want to summarize the time for... (5 Replies)
Discussion started by: ran123
5 Replies

10. Red Hat

DNS reverse lookup issue

Hi guys. Ok so let me lay out my configs. I can do a NSlookup from client to server BUT NOT a reverse lookup. DNS server: Optimus.jaydomain.com IP : 192.168.1.50 DNS Client: Megatron.jaydomain.com IP : 192.168.1.60 On Sever: # cat /etc/named.conf // // named.conf // // Provided... (4 Replies)
Discussion started by: Junaid Subhani
4 Replies
ATALKD(8)							   Netatalk 2.2 							 ATALKD(8)

NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager SYNOPSIS
atalkd [-f configfile] [-1] [-2] DESCRIPTION
atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup, and the AppleTalk Echo Protocol (similar to ping(8)). atalkd is typically started at boot time, out of /etc/rc. It first reads from its configuration file, /etc/netatalk/atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are ignored, as are blank lines. The syntax is interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ... Note that all fields except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is not given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on the command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed. The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers on the network are configured with the default zone and must agree. atalkd maps ``*'' to the default zone of the first interface. Note: The default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g. afpd, must individually specify the desired zone. See also nbp_name(3). ROUTING
If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to obtain appropriate network addresses. atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have an arbitrary list of zones associated with it. EXAMPLES
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is configured automatically from other routers on the network. The machine is the only router for the ``le1'' interface. le0 le1 -seed -net 9461-9471 -zone netatalk -zone Argus atalkd automatically acts as a router if there is more than one interface. FILES
/etc/netatalk/atalkd.conf configuration file BUGS
On some systems, atalkd can not be restarted. SEE ALSO
atalkd.conf(5) Netatalk 2.2 06 Sep 2004 ATALKD(8)
All times are GMT -4. The time now is 12:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy