On 09.05.21 14:35, Xavier Humbert via bind-users wrote:
But on one machine, it fails :
[xavier@feanor ~]$ dig @numenor dns.google.com +trace
are you aware that +trace sends queries across the servers from root to
leaf, it doesn't go through the server numenor?
couldn't get address for 'm.r
On 09/05/2021 13:44, Xavier Humbert via bind-users wrote:
On 09/05/2021 12:32, Xavier Humbert via bind-users wrote:
Hi,
My DNS system if perfectly working :
[xavier@numenor ~]$ dig dns.google.com
; <<>> DiG 9.16.15 <<>> dns.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- o
On 09/05/2021 12:32, Xavier Humbert via bind-users wrote:
Hi,
My DNS system if perfectly working :
[xavier@numenor ~]$ dig dns.google.com
; <<>> DiG 9.16.15 <<>> dns.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12276
;; flags: qr rd ra
In message <00a901c9ac92$9dc4e8a0$f9281...@wipro74039c7ca>, "Ashish" writes:
> Hi,
>
> Could someone kindly explain what is happening?
You have a DNS client that is using a pre-RFC 1535 search
algorithm that is looking up kemira.kemira.com.
Network Working Group
funet.finameserver = ns.funet.fi
funet.finameserver = ns-secondary.funet.fi
> kemira.com
Server: rockyd.rockefeller.edu
Address: 129.85.1.24
Non-authoritative answer:
kemira.com nameserver = ns1.capgemini.fi
kemira.com nameserver = ns2.capgemini.fi
Internet DNS think
5 matches
Mail list logo