No results found, please run it to get the result.
No results found, please run it to get the result.
Cached: 2022.10.20 15:34:21/ 2 years ago
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9 <<>>
near.by
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2750
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;
near.by. IN A
;; ANSWER SECTION:
near.by. 136 IN A
216.239.32.29
;; Query time: 4 msec
;; SERVER:
8.8.8.8#53(
8.8.8.8)
;; WHEN: Thu Oct 20 15:34:21 UTC 2022
;; MSG SIZE rcvd: 52
No results found, please run it to get the result.
Cached: 2022.10.20 15:34:50/ 2 years ago
PING
near.by (
216.239.32.29) 56(84) bytes of data.
64 bytes from
any-in-201d.1e100.net (
216.239.32.29): icmp_seq=1 ttl=116 time=3.71 ms
64 bytes from
any-in-201d.1e100.net (
216.239.32.29): icmp_seq=2 ttl=116 time=3.69 ms
64 bytes from
any-in-201d.1e100.net (
216.239.32.29): icmp_seq=3 ttl=116 time=3.68 ms
---
near.by ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 3.685/3.697/3.713/0.071 ms
No results found, please run it to get the result.
Cached: 2022.10.20 15:34:12/ 2 years ago
An error occurred. This command accepts IP addresses only. You can use nslookup to get the addresses of
near.by