Technology and Beyond (TaB)

Full Version: ns5.zettadom.com does not resolve
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

zma

amoners

It seems that ns5.zettadom.com can be resolved now, but I think the address is wrong. Because this domain has been pointed to hututadns0e1 whose address is 115.231.209.242.

Code:
localhost:~ amoners$ ping ns5.zettadom.com
PING ns5.zettadom.com (220.250.64.20): 56 data bytes
64 bytes from 220.250.64.20: icmp_seq=0 ttl=248 time=40.538 ms
64 bytes from 220.250.64.20: icmp_seq=1 ttl=248 time=40.391 ms
64 bytes from 220.250.64.20: icmp_seq=2 ttl=248 time=41.680 ms
64 bytes from 220.250.64.20: icmp_seq=3 ttl=248 time=53.083 ms
64 bytes from 220.250.64.20: icmp_seq=4 ttl=248 time=37.840 ms
(09-04-2015 09:57 PM)amoners Wrote: [ -> ]It seems that ns5.zettadom.com can be resolved now, but I think the address is wrong. Because this domain has been pointed to hututadns0e1 whose address is 115.231.209.242.

Code:
localhost:~ amoners$ ping ns5.zettadom.com
PING ns5.zettadom.com (220.250.64.20): 56 data bytes
64 bytes from 220.250.64.20: icmp_seq=0 ttl=248 time=40.538 ms
64 bytes from 220.250.64.20: icmp_seq=1 ttl=248 time=40.391 ms
64 bytes from 220.250.64.20: icmp_seq=2 ttl=248 time=41.680 ms
64 bytes from 220.250.64.20: icmp_seq=3 ttl=248 time=53.083 ms
64 bytes from 220.250.64.20: icmp_seq=4 ttl=248 time=37.840 ms

The name resolution seems okay now although ping does not work, yet:

---

12:56:30 llingu@kvpex0e1:/home/llingu/forest/d-thinker/container/src> ping ns5.zettadom.com
PING ns5.zettadom.com (115.231.209.242) 56(84) bytes of data.
^C
--- ns5.zettadom.com ping statistics ---
29 packets transmitted, 0 received, 100% packet loss, time 27999ms

-----

zma

Reference URL's