$ ping ntp0.dundee.ac.uk
PING ntp0.dundee.ac.uk (172.30.254.253) 56(84) bytes of data.
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): icmp_req=1 ttl=254 time=0.281 ms
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): icmp_req=2 ttl=254 time=0.303 ms
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): icmp_req=3 ttl=254 time=0.332 ms
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253): icmp_req=4 ttl=254 time=0.376 ms
^C
--- ntp0.dundee.ac.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.281/0.323/0.376/0.035 ms
$ host ntp0.dundee.ac.uk
;; connection timed out; no servers could be reached
$ nslookup ntp0.dundee.ac.uk
;; connection timed out; no servers could be reached
So ping is able to perform the name-to-IP conversion fine, but host and nslookup both fail!
Other 'normal' programs seem to perform address lookup OK (e.g. entering "www.google.com" in firefox, or even ntp if restarted later) so there is something bizarre about the network management.
It is somewhat odd, as I get this:
$ ping ntp0.dundee.ac.uk core-6513. private. dundee. ac.uk (172.30.254.253): icmp_req=1 ttl=254 time=0.281 ms core-6513. private. dundee. ac.uk (172.30.254.253): icmp_req=2 ttl=254 time=0.303 ms core-6513. private. dundee. ac.uk (172.30.254.253): icmp_req=3 ttl=254 time=0.332 ms core-6513. private. dundee. ac.uk (172.30.254.253): icmp_req=4 ttl=254 time=0.376 ms 323/0.376/ 0.035 ms
PING ntp0.dundee.ac.uk (172.30.254.253) 56(84) bytes of data.
64 bytes from 443-gb-
64 bytes from 443-gb-
64 bytes from 443-gb-
64 bytes from 443-gb-
^C
--- ntp0.dundee.ac.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 0.281/0.
$ host ntp0.dundee.ac.uk
;; connection timed out; no servers could be reached
$ nslookup ntp0.dundee.ac.uk
;; connection timed out; no servers could be reached
So ping is able to perform the name-to-IP conversion fine, but host and nslookup both fail!
Other 'normal' programs seem to perform address lookup OK (e.g. entering "www.google.com" in firefox, or even ntp if restarted later) so there is something bizarre about the network management.