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 had a reverse lookup for the server so mail was being delivered.
Recently I upgraded server to a more powerful server and this time they didn't add the server to their DNS. When I asked them about it, they offered to manage my DNS for me for a few bucks per domain or they'd delegate it to me.
I checked DynDNS and they'll manage the reverse lookup but it's a few extra bucks. May as well have the ISP manage it as it's a few bucks less if I go that way.
But I've administered bind in the past for entire address ranges so rather than pay someone else to manage it, I'd rather do it myself. Both to save a few bucks but also to keep my fingers in DNS management.
So I got my domain files set up without a problem but I'm not sure how to set up a reverse lookup file for a single or two addresses. I want to make sure it's right before I flip the switch so I thought I'd drop a quick note here and see what sort of response I get
Ultimately I believe I'd have the same two PTR records for each of the domains. And I'll contact the ISP to delegate the two IP's to my control with them as my secondary or maybe DynDNS.
So, opinions? Suggestions? Go read the Cricket book?
when we send email or try to telnet to a site that requires reverse lookup to be enabled the connection is refused.
i have the O'Reilly book DNS and Bind and in it are examples of what the reverse zone file should look like. i don't see a line that defines an email server in the example. is... (1 Reply)
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)
We have Unix configured as our external DNS, forward DNS is working properly, however Reverse lookup is not working. Any idea what the problem is? I have checked the named.boot and .rev file and everything seems to be correctly. However it appears that the reverse zone file in the named.boot... (2 Replies)
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)
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)
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)
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)
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:
... (0 Replies)
I came back to my solaris 10 system after a week of being gone and xterm no longer work. I checked into it and the system doesn't reverse lookup my client system. There is a manual entry for my system in the /etc/hosts file and a forward lookup works fine, but I still can't get reverse lookup. Any... (0 Replies)
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
LEARN ABOUT LINUX
host
HOST(1) BIND9 HOST(1)NAME
host - DNS lookup utility
SYNOPSIS
host [-aCdlnrsTwv] [-c class] [-N ndots] [-R number] [-t type] [-W wait] [-m flag] [-4] [-6] {name} [server]
DESCRIPTION
host is a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. When no arguments
or options are given, host prints a short summary of its command line arguments and options.
name is the domain name that is to be looked up. It can also be a dotted-decimal IPv4 address or a colon-delimited IPv6 address, in which
case host will by default perform a reverse lookup for that address. server is an optional argument which is either the name or IP address
of the name server that host should query instead of the server or servers listed in /etc/resolv.conf.
The -a (all) option is equivalent to setting the -v option and asking host to make a query of type ANY.
When the -C option is used, host will attempt to display the SOA records for zone name from all the listed authoritative name servers for
that zone. The list of name servers is defined by the NS records that are found for the zone.
The -c option instructs to make a DNS query of class class. This can be used to lookup Hesiod or Chaosnet class resource records. The
default class is IN (Internet).
Verbose output is generated by host when the -d or -v option is used. The two options are equivalent. They have been provided for backwards
compatibility. In previous versions, the -d option switched on debugging traces and -v enabled verbose output.
List mode is selected by the -l option. This makes host perform a zone transfer for zone name. Transfer the zone printing out the NS, PTR
and address records (A/AAAA). If combined with -a all records will be printed.
The -i option specifies that reverse lookups of IPv6 addresses should use the IP6.INT domain as defined in RFC1886. The default is to use
IP6.ARPA.
The -N option sets the number of dots that have to be in name for it to be considered absolute. The default value is that defined using the
ndots statement in /etc/resolv.conf, or 1 if no ndots statement is present. Names with fewer dots are interpreted as relative names and
will be searched for in the domains listed in the search or domain directive in /etc/resolv.conf.
The number of UDP retries for a lookup can be changed with the -R option. number indicates how many times host will repeat a query that
does not get answered. The default number of retries is 1. If number is negative or zero, the number of retries will default to 1.
Non-recursive queries can be made via the -r option. Setting this option clears the RD -- recursion desired -- bit in the query which host
makes. This should mean that the name server receiving the query will not attempt to resolve name. The -r option enables host to mimic the
behavior of a name server by making non-recursive queries and expecting to receive answers to those queries that are usually referrals to
other name servers.
By default, host uses UDP when making queries. The -T option makes it use a TCP connection when querying the name server. TCP will be
automatically selected for queries that require it, such as zone transfer (AXFR) requests.
The -4 option forces host to only use IPv4 query transport. The -6 option forces host to only use IPv6 query transport.
The -t option is used to select the query type. type can be any recognized query type: CNAME, NS, SOA, SIG, KEY, AXFR, etc. When no query
type is specified, host automatically selects an appropriate query type. By default, it looks for A, AAAA, and MX records, but if the -C
option was given, queries will be made for SOA records, and if name is a dotted-decimal IPv4 address or colon-delimited IPv6 address, host
will query for PTR records. If a query type of IXFR is chosen the starting serial number can be specified by appending an equal followed by
the starting serial number (e.g. -t IXFR=12345678).
The time to wait for a reply can be controlled through the -W and -w options. The -W option makes host wait for wait seconds. If wait is
less than one, the wait interval is set to one second. When the -w option is used, host will effectively wait forever for a reply. The time
to wait for a response will be set to the number of seconds given by the hardware's maximum value for an integer quantity.
The -s option tells host not to send the query to the next nameserver if any server responds with a SERVFAIL response, which is the reverse
of normal stub resolver behavior.
The -m can be used to set the memory usage debugging flags record, usage and trace.
IDN SUPPORT
If host has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. host
appropriately converts character encoding of domain name before sending a request to DNS server or displaying a reply from the server. If
you'd like to turn off the IDN support for some reason, defines the IDN_DISABLE environment variable. The IDN support is disabled if the
variable is set when host runs.
FILES
/etc/resolv.conf
SEE ALSO dig(1), named(8).
COPYRIGHT
Copyright (C) 2004, 2005, 2007-2009 Internet Systems Consortium, Inc. ("ISC")
Copyright (C) 2000-2002 Internet Software Consortium.
BIND9 Jun 30, 2000 HOST(1)