Sponsored Content
Full Discussion: DNS Lookup Tool Using DIG
The Lounge What is on Your Mind? DNS Lookup Tool Using DIG Post 302938324 by Neo on Saturday 14th of March 2015 10:56:04 AM
Old 03-14-2015
I fixed a small bug to make sure when a valid IPV4 address is entered, then it returns the reverse lookup.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

DNS prob - dig process

Dear MoDs, I have several doubts regarding query domain using DIG process.. below is my dig process:- ********************************************* dns-dual# /usr/bin/dig @dns-dual.surfweb.net.my my soa ; <<>> DiG 9.3.0 <<>> @dns-dual.surfweb.net.my my soa ;; global options: ... (1 Reply)
Discussion started by: unknown2205
1 Replies

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

3. Solaris

Which lookup tool query both hosts and DNS server?

As i understand, host/nslookup/dig only query DNS server to resolve name to ip. ping can query both, but it seems if ping is blocked, ping won't return IP. traceroute can query both, but i am not able to test if traceroute is blocked, What is the result? Neither ping/traceroute is... (3 Replies)
Discussion started by: honglus
3 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. 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

7. IP Networking

lookup ip address, subnet mask, gateway, and dns at same time

Is there a command that can lookup ip address, subnet mask, gateway, and dns all at the same. I know ifconfig can lookup ip address and subnet mask. I know route -n can lookup gateway. Not sure about a dns command. So I hope there is a way to lookup ip address, subnet mask, gateway, and dns all at... (2 Replies)
Discussion started by: cokedude
2 Replies

8. IP Networking

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: ... (0 Replies)
Discussion started by: scheruga
0 Replies

9. IP Networking

DNS: Dig returns different responses...

Hey everyone, Okay, so I've been having some fun with the dig command, and wanted to dig my old school. Two questions came up from this. So I: dig @8.8.8.8 +recurse njcu.edu ANY and the result is about 8 records, including the SOA record. One of them is this weird TXT record, and the other is... (1 Reply)
Discussion started by: Lost in Cyberia
1 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
iptunnel(8)						      System Manager's Manual						       iptunnel(8)

NAME
iptunnel - Creates, deletes, and displays configured tunnels SYNOPSIS
/usr/sbin/iptunnel [operation] [args] DESCRIPTION
The iptunnel command creates configured tunnels for sending and receiving IPV6 or IPV4 packets that are encapsulated as the payload of an IPV4 datagram. The iptunnel command can perform one of the following operations: Creates a tunnel interface, which you must subsequently configure by using the ifconfig command. The syntax of the create operation is as follows: iptunnel create [-I int-name] [v4-dest] [v4-src] Specifies the interface unit of the tunnel to be created. This is an optional parameter. The int-name parameter has the following form: iptx, where x is the interface unit number. By default, the interface name selected for the tunnel is iptx+1, or the value of the interface unit number of the last tunnel created plus 1. Specifies the remote end-point to which a tunnel is to be created. Sets the IPV4 source address in the encapsulating header. The tunnel is enabled (packets are sent/received on the tunnel) only if v4-src is a valid address on the system. This is an optional parameter. Deletes a tunnel interface. You must disable the tunnel before you can delete it by executing the following command: # ifconfig tunnel name down delete abort Shows the tunnel attributes (name, tunnel end points, next hop for tunneled packets). EXAMPLES
To create a tunnel from hobbes to calvin, enter: # iptunnel create -I ipt5 calvin ipt5 iftype 208 src 16.140.16.86 dst 16.140.16.91 To display the tunnel attributes, enter: # iptunnel show ipt5 interface ipt5 src 16.140.16.86 dst 16.140.16.91 gate 16.140.16.86 To config- uring the tunnel to encapsulate IPv6 packets, enter: # ifconfig ipt5 ipv6 up IPv6 packets will be sent as payloads of IPv4 datagrams from 16.140.16.86 to 16.140.16.91. The tunnel may also be used to send IPV4 packets encapsulated within IPV4 headers as follows: # ifconfig ipt5 10.10.80.60 netmask 255.255.255.0 To verify the previous command, enter: # ifconfig ipt5 ipt5: flags=4c1<UP,RUNNING,NOARP,MULTICAST> 16.140.16.86 --> 16.140.16.91 rxmt 1000, reach time 30000, dad tries 1, mtu 1280, hops 64, token len 64 inet 10.10.80.60 netmask ffffff00 ipmtu 1280 inet6 fe80::108c:1056 To deleting the tunnel, enter: # ifconfig ipt5 down delete abort ipt5: delete inet address 10.10.80.60 10.10.80.60: aborting 0 tcp connection(s) Then, enter: # iptunnel delete ipt5 interface ipt5 deleted SEE ALSO
Commands: ifconfig(8). RFC 2003, IP Encapsulation within IP, Perkins, C., October 1996 iptunnel(8)
All times are GMT -4. The time now is 01:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy