That is great feedback, it indicates that we have some underlying setup problem on our Linux system/firewall whatever, maybe a packet sizing issue or firewall port 53, those are indicated in postings.
Thanks for trying it out.
---------- Post updated at 09:48 AM ---------- Previous update was at 09:44 AM ----------
This works too:
So that further indicates an issue with our own DNS setup..
Can I use two different DNS servers in the one command in the form of primary and secondary.
Take this for example:
dig @<primaryAddress> @<secondaryAddress> MX domain.tld
So if primary address is down, it will use the secondary address as a backup. It seems to work when testing, but thought... (1 Reply)
Hi All,
Can please let me know what is the difference between the single line mode and multi line mode in regular expresions?
Thanks,
Chidhambaram B (3 Replies)
Hi,
I have these entries in the /etc/esolv.conf:
------------
domain xxxxxx
search yyyyyy
nameserver 127.0.0.1
nameserver aaaaaaaaaaaaaaaa
nameserver bbbbbbbbbbbbbbbb
-------------
When I use 'dig' or 'nslookup' command, like 'dig yahoo.com' it uses the localhost as the server.
I... (2 Replies)
I am relatively new to this forum and Unix scripting.
ksh script:
part 1 :will call a PL\SQL program will create 3 CSV file at the unix directory.
part 2 : will sftp the files to the EFT server.
Once the EFT server receives these file , it will transfer them to a shared windows folders.
... (3 Replies)
Dear All,
I want to get all the IPs of the A RECORDS for mail.google.com.
The aim is to deny access to these IPs.
I learnt that mail.google.com has several IPs.
I did the following steps:
1. whois google.com
2. I got the following as its DOMAIN SERVERS:
3.# dig @ns1.google.com a... (1 Reply)
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)
Hi,
I am testing some code to match a grep to see if one of the dns server exists but it does not seem to match:
ERROR:
=======
CRITICAL: google.com DNS : ns3.google.com NOT found
CODE:
=====
if ; then
echo "OK: google.com DNS : ns3.google.com exists"
else
echo... (5 Replies)
Hi there, I'm currently working on an exercise to connect to a Windows iscsi target via a Red Hat initiator machine. I'm using Windows Server 2012 and Red Hat Enterprise Linux v7.1
I have created the target on the Windows Server box and the two devices can communicate with each other. Verified... (3 Replies)
Discussion started by: Tech87
3 Replies
LEARN ABOUT OSF1
trpt
trpt(8) System Manager's Manual trpt(8)NAME
trpt - Transliterates protocol trace
SYNOPSIS
trpt [-afjst] [-p address]
FLAGS
Print the values of the source and destination addresses for each packet recorded, in addition to the normal output. Follows the trace as
it occurs, waiting briefly for additional records each time the end of the log is reached. Lists the protocol control block addresses for
which trace records exist. Shows only trace records associated with the protocol control block specified in hexadecimal by the address
variable.
You must include a space between the -p flag and the address variable when you specify this flag. Prints a detailed description of
the packet-sequencing information, in addition to the normal output. Prints the values for all timers at each point in the trace,
in addition to the normal output.
DESCRIPTION
The trpt command, used for debugging sockets, queries the buffer of Transmission Control Protocol (TCP) trace records. The TCP trace
record buffer is created when a socket is marked for debugging with the setsockopt(2) subroutine. The trpt command queries the buffer and
then prints a description of the trace records.
When you specify no options, the trpt command prints all the trace records found in the system and groups them according to their TCP/IP
connection Protocol Control Block (PCB).
If you are debugging a system file other than the default, the system argument can be used to replace the default.
Before you can use the trpt command, you must do the following: Isolate the problem and mark for debugging the socket or sockets involved
in the connection. Find the address of the protocol control blocks associated with these sockets by using the netstat -aA command. Then,
you can run the trpt command, using the -p flag to supply the associated protocol control block addresses. You can specify multiple -p
address flags with a single trpt command.
The -f flag can be used to follow the trace log once it is located. The -j flag can be used to check for the presence of trace records for
the socket in question.
If the system image does not contain the proper symbols to find the trace buffer, the trpt command cannot succeed.
FILES
Specifies the command path
RELATED INFORMATION
Commands: netstat(1)
Functions: setsockopt(2) delim off
trpt(8)