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 ULTRIX
trpt
trpt(8c)trpt(8c)Name
trpt - transliterate protocol trace
Syntax
trpt [ -a ] [ -s ] [ -t ] [ -j ] [ -p hex-address ] [ system [ core ] ]
Description
The command interrogates the buffer of TCP trace records created when a socket is marked for debugging and prints a readable description of
these records.
Options
When no options are supplied, prints all the trace records found in the system grouped according to TCP connection protocol control block
(PCB). The following options may be used to alter this behavior:
-s In addition to the normal output, prints a detailed description of the packet sequencing information.
-t In addition to the normal output, prints the values for all timers at each point in the trace.
-j Gives a list of the protocol control block addresses for which there are trace records.
-p Shows only trace records associated with the protocol control block whose address follows.
-a In addition to the normal output, prints the values of the source and destination addresses for each packet recorded.
The recommended use of is to isolate the problem and enable debugging on the socket(s) involved in the connection. Find the address of the
protocol control blocks associated with the sockets using the -A option to Then run with the -p option, supplying the associated protocol
control block addresses. If there are many sockets using the debugging option, the -j option may be useful in checking to see if any trace
records are present for the socket in question.
If debugging is being performed on a system or core file other than the default, the last two arguments may be used to supplant the
defaults.
Diagnostics
no namelist
The system image does not contain the proper symbols to find the trace buffer.
Other diagnostic messages are self-explanatory.
FilesSee Alsonetstat(1), setsockopt(2)trpt(8c)