One of our email recipients has 17 mx records, and our emailing program postfix on linux does not retrieve these records. When using dig, the same thing happens.
This command returns no mx records
But when using +trace, the records get returned
The question is whether there is a setting we can make to make the standard mx lookup work properly.
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 DEBIAN
sip-dig
sip-dig(1) sofia-sip-utils sip-dig(1)NAME
sip-dig - Resolve SIP URIs. This is an example program for sresolv library in synchronous mode.
Author:
Pekka Pessi <Pekka.Pessi@nokia.com>
Date:
Original Created: Tue Jul 16 18:50:14 2002 ppessi
Synopsis
sip-dig [OPTIONS] uri...
Description
The sip-dig utility resolves SIP URIs as described in RFC 3263. It queries NAPTR, SRV and A/AAAA records and prints out the resulting
transport addresses.
The default transports are: UDP, TCP, SCTP, TLS and TLS-SCTP. The SIPS URIs are resolved using only TLS transports, TLS and TLS-SCTP. If
not otherwise indicated by NAPTR or SRV records, the sip-dig uses UDP and TCP as transports for SIP and TLS for SIPS URIs.
The results are printed intended, with a preference followed by weight, then protocol name, port number and IP address in numeric format.
Command Line Options
The sip-dig utility accepts following command line options:
-p protoname
Use named transport protocol. The protoname can be either well-known, e.g., 'udp', or it can specify NAPTR service and SRV identifier,
e.g., 'tls-udp/SIPS+D2U/_sips._udp.'.
--udp
Use UDP transport protocol.
--tcp
Use TCP transport protocol.
--tls
Use TLS over TCP transport protocol.
--sctp
Use SCTP transport protocol.
--tls-sctp
Use TLS over SCTP transport protocol.
--no-sctp
Ignore SCTP or TLS-SCTP records in the list of default transports. This option has no effect if transport protocols has been explicitly
listed.
-4 Query IP4 addresses (A records)
-6 Query IP6 addresses (AAAA records).
-v Be verbatim.
Return Codes
0when successful (a 2XX-series response is received) 1when unsuccessful (a 3XX..6XX-series response is received) 2initialization failure
Examples
Resolve sip:openlaboratory.net, prefer TLS over TCP, TCP over UDP:
$ sip-dig --tls --tcp --udp sip:openlaboratory.net
1 0.333 tls 5061 212.213.221.127
2 0.333 tcp 5060 212.213.221.127
3 0.333 udp 5060 212.213.221.127
Resolve sips:example.net with TLS over SCTP (TLS-SCTP) and TLS:
$ sip-dig -p tls-sctp --tls sips:example.net
1 0.500 tls-udp 5061 172.21.55.26
2 0.500 tls 5061 172.21.55.26
Environment
#SRESOLV_DEBUG, SRESOLV_CONF
Reporting Bugs
Report bugs to <sofia-sip-devel@lists.sourceforge.net>.
Author
Written by Pekka Pessi <pekka -dot pessi -at- nokia -dot- com>
Copyright
Copyright (C) 2006 Nokia Corporation.
This program is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Version 1.12.11devel Sat May 7 2011 sip-dig(1)