On 13/04/2021 18:52, Tim via users wrote:
You can see that sort of thing with the "dig" tool. If you
do a "dig
example.com" you'll get a collection of responses. The "answer"
section is the domain name and numerical IP address for it, that you
queried. The "authority" section will be the authoritative name
servers for those records (the master host for them). An "additional"
section which can provide info about those authoritative servers. And
in the last bit will be the "SERVER" that directly answered your query.
One has to be somewhat careful as to the actual dig command used.
By default the type searched are A records. So, if your domain name is also the name of
a host then you'd need to use "dig -tany domainname"
example:
[egreshko@meimei ~]$ dig
ibm.com
ibm.com. 19 IN A 104.115.95.17
[egreshko@meimei ~]$ dig -tany
ibm.com
ibm.com. 20 IN AAAA 2600:1417:1800:289::3831
ibm.com. 20 IN AAAA 2600:1417:1800:286::3831
ibm.com. 3600 IN MX 5
mx0b-001b2d01.pphosted.com.
ibm.com. 3600 IN MX 5
mx0a-001b2d01.pphosted.com.
ibm.com. 86061 IN SOA
asia3.akam.net.
dnsadm.us.ibm.com.
1564134810 43200 7200 604800 3600
etc.....
Also, if you are running a DNS server to for "local" addresses in your domain
and your system's configuration
points to the local server you would most likely want to add the @server parameter to make
sure you get
the "external" information.
[egreshko@meimei ~]$ dig -tany
meimei.greshko.com
meimei.greshko.com. 86400 IN A 192.168.1.18
meimei.greshko.com. 86400 IN AAAA 2001:b030:112f::140e
[egreshko@meimei ~]$ dig @8.8.8.8 -tany
meimei.greshko.com
meimei.greshko.com. 1199 IN A 211.75.128.214
meimei.greshko.com. 1199 IN AAAA 2001:b030:112f::140e
--
Remind me to ignore comments which aren't germane to the thread.