Sponsored Content
Operating Systems Solaris Which lookup tool query both hosts and DNS server? Post 302277304 by pludi on Friday 16th of January 2009 02:09:09 AM
Old 01-16-2009
Neither ping nor traceroute query the host you're trying to reach, they too use DNS to resolve the name to an IP.
 

10 More Discussions You Might Find Interesting

1. IP Networking

dns and hosts file

ok i have a question now when i add machines on network that are running unix do i add them in the /etc/hosts file also include them in dns (4 Replies)
Discussion started by: rmuhammad
4 Replies

2. UNIX for Advanced & Expert Users

Virtual Hosts and Alteon DNS conflicts

Hi, This is more of a verification rather than a question of technical nature. This is based on solaris 10 machine Could we use Virtual hosts (within our hosts file): 123.1.1.10 virtual_host_name 123.1.1.10 host_A (note: 123.1.1.10 - host_A is also in our DNS server entry) And... (0 Replies)
Discussion started by: jackola
0 Replies

3. 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

4. AIX

prevent sendmail do DNS lookup

Hello! How do I prevent AIX sendmail from doing a DNS lookup prior sending the mail? (we still need to have the DNS resolving on AIX level). We are running AIX 6.1 and 5.3. //sap4ever (1 Reply)
Discussion started by: sap4ever
1 Replies

5. Programming

How to set DNS lookup type for getaddrinfo()?

Hi there, I'm trying to do an MX type lookup using getaddrinfo(), but I can't work out how to change the lookup type to MX from the standard A - can anybody tell me how to do this? Thanks very much John G (3 Replies)
Discussion started by: JohnGraham
3 Replies

6. UNIX for Dummies Questions & Answers

Checking for unix hosts that do not have reverse lookup

Hi there i am not sure how to explain my problem. i need to run a script to give me the results of all my unix hosts that do not have reverse lookup activated (for lack of a better word), i need to give this to out Server guys to add it part of the AD rules. So what i need is a script to... (0 Replies)
Discussion started by: brian112
0 Replies

7. Solaris

DNS Lookup failure:

I am facing typical problem with apache as proxy. my solaris box was running with apache1.3, due to security issue i have updated to apache 2.2. I don't have any DNS set up onmy network. I was able to connect to internet apache 1.3 working as proxy server. http and https are working fine. when... (3 Replies)
Discussion started by: sns_sns
3 Replies

8. 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

9. AIX

Use of /etc/hosts files in resolving the dns name

Hello, For what purpose /etc/hosts file is used.I mean how any request coming to a DNS server or a switch would know that which name and ip are configured in /etc/hosts files of a server? Best regards, Vishal (3 Replies)
Discussion started by: admin_db
3 Replies

10. What is on Your Mind?

DNS Lookup Tool Using DIG

Hi. Having a bit of quick fun putting some networking tools online. Here is a DNS Lookup tool. It's basically the DIG command line tool wrapped in forum formatting. If you want more features, please post here. I'm doing to make a few more network tools like this and move on to other... (1 Reply)
Discussion started by: Neo
1 Replies
host(1) 						      General Commands Manual							   host(1)

NAME
host - DNS lookup utility SYNOPSIS
class] ndots] number] type] wait] name [server] DESCRIPTION
is a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. With no options or operands, prints an annotated usage summary. Options Use only the IPv4 query transport. Use only the IPv6 query transport. Equivalent to using Attempt to display the records for zone name from all the listed authoritative name servers for that zone. The list of name servers is defined by the records that are found for the zone. Make a DNS query of class class. This can be used to look up class resource records. The values for class are: The Internet class (default). The MIT Chaosnet class. The MIT Athena Hesiod class. The class values are case-insensitive. Generate verbose output. Now equivalent to the option. is provided for backwards compatibility. In previous versions, it switched on debugging traces. Use the IP6.INT domain, as defined in RFC 1886, to perform reverse lookups of IPv6 addresses. The default is to use IP6.ARPA. Select list mode. performs a zone transfer for zone name. Transfer the zone, printing out the and address records If is combined with all records will be printed. Set the number of dots that have to be in name for it to be considered absolute. The default value is defined using the statement in or is if no statement is present. Names with fewer dots are interpreted as relative names and will be searched for in the domains listed in the or directive in Set the number of UDP retries for a lookup. number indicates how many times 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 is set to 1. Make nonrecursive queries. Setting this option clears the RD (recursion desired) bit in the query which makes. This should mean that the name server receiving the query will not attempt to resolve the name operand. This option enables to mimic the behavior of a name server by making nonrecursive queries and expecting to receive answers to those queries that are usually referrals to other name servers. Use a TCP connection when querying the name server. TCP is automatically selected for queries that require it, such as zone transfer requests. By default uses UDP when making queries. Select the query type. type can be any recognized query type: and so on. For potential values, see the command in nslookup(1) and the discussion in named.conf(4). The type values are case-insensitive. When the option is omitted, automatically selects an appropriate query type. By default, it looks for records, but if the option is given, queries are made for records. If the operand is an IPv4 or IPv6 address, queries for records. For a query type of you can specify the starting serial number by appending an equals sign followed by the starting serial number (for example, Generate verbose output. Set the time to wait for a reply to wait seconds. If wait is less than 1, the wait interval is set to 1. Effectively wait forever for a reply. The time to wait for a response is set to the number of seconds given by the hardware's maximum value for an integer quantity. Operands name The domain name that is to be looked up. It can also be an IPv4 or IPv6 address, in which case will, by default, perform a reverse lookup for that address. server The name or IP address of the name server that should query. The default is the server or servers listed in EXAMPLES
Using a host name: Using an IP address: AUTHOR
was developed by the Internet Systems Consortium (ISC). FILES
SEE ALSO
dig(1), nslookup(1), named(1M), named.conf(4), resolver(4). Requests for Comments (RFC): 1886, available online at available online at available from the Internet Systems Consortium at BIND 9.3 host(1)
All times are GMT -4. The time now is 04:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy