Hi, Just pointing out to other responding to this thread that I was referring to the *query* response times, I said nothing about ICMP which is perfectly fine.
So please stop responding with ping response times already :-) No, pfSense does not set these per default, they are in wide use because these are part of the Google DNS whitelist for V6 records. Op 4 jan 2012, om 21:33 heeft Mark Kamichoff het volgende geschreven: > ;; ANSWER SECTION: > cnn.com. 299 IN A 157.166.226.26 > cnn.com. 299 IN A 157.166.255.19 > cnn.com. 299 IN A 157.166.255.18 > cnn.com. 299 IN A 157.166.226.25 And a similar mistake I see others respond too as well, this is another domain with just a IPv4 record. That was not really what I was complaining about but I was not specific enough in my email When requesting the DNS for the hostname with a Quad A the story is entirely different! Try www.pfsense.com or www.didi.nl Those will definitely hit the issue, otherwise one can always use Nanog.org like below. 74.82.42.42 2204 msec 2001:4860:4860::8844 17 msec 2001:470:20::2 2890 msec Best regards, Seth > > ;; Query time: 38 msec > ;; SERVER: 74.82.42.42#53(74.82.42.42) > ;; WHEN: Wed Jan 4 15:27:17 2012 > ;; MSG SIZE rcvd: 89 > > (neodymium:15:32)% dig @2001:470:20::2 cnn.com. A > > ; <<>> DiG 9.7.3 <<>> @2001:470:20::2 cnn.com. A > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41382 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;cnn.com. IN A > > ;; ANSWER SECTION: > cnn.com. 295 IN A 157.166.226.25 > cnn.com. 295 IN A 157.166.255.18 > cnn.com. 295 IN A 157.166.255.19 > cnn.com. 295 IN A 157.166.226.26 > > ;; Query time: 20 msec > ;; SERVER: 2001:470:20::2#53(2001:470:20::2) > ;; WHEN: Wed Jan 4 15:32:27 2012 > ;; MSG SIZE rcvd: 89 > > That being said, keep in mind these are anycasted. I'm using > 216.66.22.2 [tserv13.ash1.ipv6.he.net] for IPv4 and 209.51.161.14 > [tserv4.nyc4.ipv6.he.net] according to the A record returned by > whoami.akamai.net. I might not be hitting the same server you are. > > - Mark > > -- > Mark Kamichoff > p...@prolixium.com > http://www.prolixium.com/