10 More Discussions You Might Find Interesting
1. Red Hat
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
2. Shell Programming and Scripting
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
3. IP Networking
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
4. UNIX for Advanced & Expert Users
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
5. Shell Programming and Scripting
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
6. UNIX for Advanced & Expert Users
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
7. IP Networking
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
8. Programming
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
9. IP Networking
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
10. IP Networking
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
dns(n) dns dns(n)
NAME
dns - Tcl Domain Name Service Client
SYNOPSIS
package require Tcl 8.2
package require dns ?1.0.1?
::dns::resolve query ?options?
::dns::configure ?options?
::dns::name token
::dns::address token
::dns::cname token
::dns::status token
::dns::error token
::dns::reset token
::dns::wait token
::dns::cleanup token
DESCRIPTION
The dns package provides a Tcl only Domain Name Service client. You should refer to RFC 1034 and RFC 1035 for information about the DNS
protocol or read resolver(3) to find out how the C library resolves domain names. The intention of this package is to insulate Tcl scripts
from problems with using the system library resolver for slow name servers. It may or may not be of practical use. The package also
extends the package uri to support DNS URIs or the form dns:what.host.com or dns://my.nameserver/what.host.com. The dns::resolve command
can handle DNS URIs or simple domain names as a query.
Note: This package uses TCP to query DNS servers as the tcl core does not implement UDP networking. This means that this module will not
work if DNS over TCP is blocked by a firewall, or not accepted by the chosen nameserver.
COMMANDS
::dns::resolve query ?options?
Resolve a domain name using the DNS protocol. query is the domain name to be lookup up. This should be either a fully qualified
domain name or a DNS URI.
-nameserver hostname or -server hostname
Specify an alternative name server for this request.
-protocol tcp|udp
Specify the network protocol to use for this request. Can be one of tcp or udp. However only tcp is currently implemented in
the package.
-port portnum
Specify an alternative port.
-search domainlist
-timeout milliseconds
Override the default timeout.
-type TYPE
Specify the type of DNS record you are interested in. Valid values are A, NS, MD MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR,
HINFO, MINFO, MX, TXT, AXFR, MAILB, MAILA and *. See RFC1035 for details about the return values.
-class CLASS
Specify the class of domain name. This is usually IN but may be one of IN for internet domain names, CS, CH, HS or * for any
class.
-recurse boolean
Set to false if you do not want the name server to recursively act upon your request. Normally set to true.
-command procname
Set a procedure to be called upon request completion. The procedure will be passed the token as its only argument.
::dns::configure ?options?
The ::dns::configure command is used to setup the dns package. The server to query, the protocol and domain search path are all set
via this command. If no arguments are provided then a list of all the current settings is returned. If only one argument then it
must the the name of an option and the value for that option is returned.
-nameserver hostname
Set the default name server to be used by all queries. The default is localhost.
-protocol tcp|udp
Set the default network protocol to be used. Defaults to tcp.
-port portnum
Set the default port to use on the name server. The default is 53.
-search domainlist
Set the domain search list. This is currently not used.
-timeout milliseconds
Set the default timeout value for DNS lookups. Defaults to 30 seconds.
::dns::name token
Returns a list of all domain names returned as an answer to your query.
::dns::address token
Returns a list of the address records that match your query.
::dns::cname token
Returns a list of canonical names (usually just one) matching your query.
::dns::status token
Returns the status flag. For a successfully completed query this will be ok. May be error or timeout or eof. See also ::dns::error
::dns::error token
Returns the error message provided for requests whose status is error. If there is no error message then an empty string is
returned.
::dns::reset token
Reset or cancel a DNS query.
::dns::wait token
Wait for a DNS query to complete and return the status upon completion.
::dns::cleanup token
Remove all state variables associated with the request.
EXAMPLES
% set tok [dns::resolve www.tcl.tk]
::dns::1
% dns::status $tok
ok
% dns::address $tok
199.175.6.239
% dns::name $tok
www.tcl.tk
Using DNS URIs as queries:
% set tok [dns::resolve "dns:tcl.tk;type=MX"]
% set tok [dns::resolve "dns://l.root-servers.net/www.tcl.tk"]
SEE ALSO
resolver(5)
AUTHORS
Pat Thoyts
KEYWORDS
DNS, resolver, domain name service
dns 1.0.1 dns(n)