Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- So, I can ping the OpenNIC custom TLD websites like grep.geek, be.libre and blahdns.oss just fine... but nic.fur gives nothing but errors:
- On Nighthawk (my OpenWRT router):
- root@Nighthawk:~# ping nic.fur
- PING nic.fur (2a01:4f8:1c1c:f114::1): 56 data bytes
- 64 bytes from 2a01:4f8:1c1c:f114::1: seq=0 ttl=47 time=117.375 ms
- ^C
- --- nic.fur ping statistics ---
- 1 packets transmitted, 1 packets received, 0% packet loss
- round-trip min/avg/max = 117.375/117.375/117.375 ms
- root@Nighthawk:~# ping -4 nic.fur
- PING nic.fur (49.12.203.237): 56 data bytes
- 64 bytes from 49.12.203.237: seq=0 ttl=46 time=120.588 ms
- ^C
- --- nic.fur ping statistics ---
- 1 packets transmitted, 1 packets received, 0% packet loss
- round-trip min/avg/max = 120.588/120.588/120.588 ms
- root@Nighthawk:~# ping -4 grep.geek
- PING grep.geek (161.97.219.84): 56 data bytes
- 64 bytes from 161.97.219.84: seq=0 ttl=53 time=57.884 ms
- ^C
- --- grep.geek ping statistics ---
- 1 packets transmitted, 1 packets received, 0% packet loss
- round-trip min/avg/max = 57.884/57.884/57.884 ms
- root@Nighthawk:~# ping -6 grep.geek
- PING grep.geek (2001:470:4212:1::254): 56 data bytes
- 64 bytes from 2001:470:4212:1::254: seq=0 ttl=55 time=76.070 ms
- ^C
- --- grep.geek ping statistics ---
- 2 packets transmitted, 1 packets received, 50% packet loss
- round-trip min/avg/max = 76.070/76.070/76.070 ms
- root@Nighthawk:~#
- Let's see how my Windows 10 laptop fares in this...
- C:\# ping -4 grep.geek
- Pinging grep.geek [161.97.219.84] with 32 bytes of data:
- Reply from 161.97.219.84: bytes=32 time=52ms TTL=52
- Reply from 161.97.219.84: bytes=32 time=53ms TTL=52
- Reply from 161.97.219.84: bytes=32 time=52ms TTL=52
- Reply from 161.97.219.84: bytes=32 time=52ms TTL=52
- Ping statistics for 161.97.219.84:
- Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
- Approximate round trip times in milli-seconds:
- Minimum = 52ms, Maximum = 53ms, Average = 52ms
- C:\# ping -6 grep.geek
- Pinging grep.geek [2001:470:4212:1::254] with 32 bytes of data:
- Reply from 2001:470:4212:1::254: time=82ms
- Reply from 2001:470:4212:1::254: time=81ms
- Reply from 2001:470:4212:1::254: time=81ms
- Reply from 2001:470:4212:1::254: time=86ms
- Ping statistics for 2001:470:4212:1::254:
- Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
- Approximate round trip times in milli-seconds:
- Minimum = 81ms, Maximum = 86ms, Average = 82ms
- Okay... now let's try getting to nic.fur:
- root@Nighthawk:~# ping -4 nic.fur
- PING nic.fur (49.12.203.237): 56 data bytes
- 64 bytes from 49.12.203.237: seq=0 ttl=46 time=119.939 ms
- 64 bytes from 49.12.203.237: seq=1 ttl=46 time=117.486 ms
- 64 bytes from 49.12.203.237: seq=2 ttl=46 time=119.322 ms
- ^C
- --- nic.fur ping statistics ---
- 4 packets transmitted, 3 packets received, 25% packet loss
- round-trip min/avg/max = 117.486/118.915/119.939 ms
- root@Nighthawk:~# ping -6 nic.fur
- PING nic.fur (2a01:4f8:1c1c:f114::1): 56 data bytes
- 64 bytes from 2a01:4f8:1c1c:f114::1: seq=0 ttl=49 time=137.825 ms
- 64 bytes from 2a01:4f8:1c1c:f114::1: seq=1 ttl=49 time=136.332 ms
- 64 bytes from 2a01:4f8:1c1c:f114::1: seq=2 ttl=49 time=140.319 ms
- 64 bytes from 2a01:4f8:1c1c:f114::1: seq=3 ttl=49 time=136.029 ms
- ^C
- --- nic.fur ping statistics ---
- 4 packets transmitted, 4 packets received, 0% packet loss
- round-trip min/avg/max = 136.029/137.626/140.319 ms
- Huh.. so it works from the router.... let's see if it works from the Windows 10 Laptop...
- C:\# ping -4 nic.fur
- Ping request could not find host nic.fur. Please check the name and try again.
- C:\# ping -6 nic.fur
- Ping request could not find host nic.fur. Please check the name and try again.
- C:\# ping nic.fur
- Ping request could not find host nic.fur. Please check the name and try again.
- Okay, what's going on... why is this the case?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement