Thursday, 22 November 2012

Is Google DNS a Myth?

Google public DNS resolving services on IP addresses 8.8.8.8 and 8.8.4.4 was sold as being a faster solution for users, since caching could occur on a massive scale, but is it just a statistics gathering exercise for Google?

Using NameBench (http://code.google.com/p/namebench/), and running the test, it looks as if Google DNS is actually slower than local services, and popular global ones:


Mean Response Duration

Mean Duration Graph

Fastest Individual Response Duration

Fastest Response Graph

Response Distribution Chart (First 200ms)

Response Distribution Graph (first 200ms)

Response Distribution Chart (Full)

Response Distribution Graph (full)

DNS Speed testing.

DNS Speed testing.

I've often used ZoneCheck to test if DNS is set up correctly, but it doesn't give an indication of performance,
for that, I'd recommend https://www.ultratools.com/tools/dnsHostingSpeedResult - Check for "A" record response, where you should aim to get a response time of 50ms or less.

Here is a speed check of this blog, which is hosted by Google.


freenameservers.blogspot.co.uk

Name ServerAAAACNAMEMXSOAASPFSRVTXT
ns3.google.com.3830383131313139
ns4.google.com.32333233
ns2.google.com.1313131314121313
ns1.google.com.1615171616161716
Min. Time(ms)32333233
Max. Time(ms)3830383131313139
Avg. Time(ms)1715171516151617

co.uk.

ns5.nic.uk.85 ms
nsa.nic.uk.10 ms
ns4.nic.uk.87 ms
ns2.nic.uk.88 ms
ns1.nic.uk.101 ms
ns7.nic.uk.82 ms
ns6.nic.uk.88 ms
nsb.nic.uk.2 ms
nsd.nic.uk.10 ms
nsc.nic.uk.2 ms
ns3.nic.uk.80 ms
Min. Time: 2 ms  Max. Time: 101 ms  Avg. Time: 57 ms

TLD Servers

ns4.nic.uk.79 ms
ns1.nic.uk.101 ms
ns3.nic.uk.91 ms
ns2.nic.uk.86 ms
ns6.nic.uk.90 ms
nsc.nic.uk.2 ms
ns5.nic.uk.86 ms
nsa.nic.uk.10 ms
nsd.nic.uk.10 ms
nsb.nic.uk.2 ms
ns7.nic.uk.82 ms
Min. Time: 2 ms  Max. Time: 101 ms  Avg. Time: 58 ms

Root Servers

h.root-servers.net. (H3)5 ms
k.root-servers.net. (k3.linx.k.ripe.net)97 ms
a.root-servers.net. ()231 ms
c.root-servers.net. (iad1a.c.root-servers.org)2 ms
l.root-servers.net. (dnd01.l.root-servers.org)92 ms
e.root-servers.net. (e5.arc.nasa.gov)80 ms
m.root-servers.net. (M-CDG-1)85 ms
i.root-servers.net. (s1.bnx)92 ms
f.root-servers.net. (scl1a.f.root-servers.org)166 ms
d.root-servers.net. (css-d.net.umd.edu)3 ms
b.root-servers.net. (b8)65 ms
j.root-servers.net. (jluepe1-elstk2)139 ms
g.root-servers.net. (g.root-servers2.net)35 ms
Min. Time: 2 ms  Max. Time: 231 ms  Avg. Time: 84 ms

Monday, 28 May 2012

.VE Domains down



As of 3 PM GMT, all Venezuelan domains (.ve) appear to have gone down. It does appear that the sole nameserver responsible for .com.ve is unresponsive:

nslookup -q=ns com.ve
Server:  my.router
Address:  192.168.1.1

ve
        primary name server = ns1.nic.ve
        responsible mail addr = hostmaster.nic.ve
        serial  = 2012052809
        refresh = 900 (15 mins)
        retry   = 300 (5 mins)
        expire  = 1296000 (15 days)
        default TTL = 3600 (1 hour)

C:\Users\Administrator>ping ns1.nic.ve
Ping request could not find host ns1.nic.ve.


Saturday, 28 April 2012

Manage DNS from your iPhone or iPad



Manage DNS from your iPhone, All the features of www.freenameservers.co.uk in one app:
http://itunes.apple.com/us/app/dns-manager/id521448034

Wednesday, 25 April 2012

Manage DNS from your Nokia phone

If you have a Nokia phone, then we've just developed a new App for the Nokia OVI store that allows you manage the DNS settings for your domain.






Here is the Nokia OVI store Link: http://store.ovi.com/content/272883

Friday, 8 April 2011

Reverse DNS lookup using nslookup

It's easy to get the IP address from a domain name, just ping it.

C:\Users\Administrator>ping s15243155.onlinehome-server.info

Pinging s15243155.onlinehome-server.info [212.227.102.68] with 32 bytes of data

Or use nsLookup to get the A record, which does the same

C:\Users\Administrator>nslookup -q=a s15243155.onlinehome-server.info
Server: my.router
Address: 192.168.1.1

Non-authoritative answer:
Name: s15243155.onlinehome-server.info
Address: 212.227.102.68

To reverse the lookup, then you use the special "in-arpa.arpa" domain with the IP address backwards... like this

C:\Users\Administrator>nslookup -q=ptr 68.102.227.212.in-addr.arpa
Server: my.router
Address: 192.168.1.1

Non-authoritative answer:
68.102.227.212.in-addr.arpa name = s15243155.onlinehome-server.info

102.227.212.in-addr.arpa nameserver = nsa2.schlund.de
102.227.212.in-addr.arpa nameserver = nsa.schlund.de
nsa.schlund.de internet address = 195.20.224.98
nsa2.schlund.de internet address = 195.20.244.5

This really comes into play when fixing this error in ZoneCheck:

w: Reverse for the nameserver IP address doesn't match
  • ns1.xyz.net/86.xx.xx.194
To Fix this, click Start>Run>dnsmgmt.msc

Select Reverse Lookup zones, select the .in-addr.arpa.

Right Click, Select "New Pointer (PTR)", enter the first 3 digits of the IP into the "Host IP Address" and enter the nameserver domain into "Host name", then press OK




Thursday, 24 February 2011

xn--j6w193g The new Hong Kong IDN (香港)

The HKDNR is releasing the new Chinese IDN top level domain for Hong Kong (香港) on the 10 March, 2011.

The punycode version of this domain is xn--j6w193g with the following DNS infrastructure:

xn--j6w193g nameserver = NS2.CUHK.EDU.HK
xn--j6w193g nameserver = NS1.HKIRC.NET.HK
xn--j6w193g nameserver = ADNS1.BERKELEY.EDU
xn--j6w193g nameserver = HK-NS.PCH.NET
xn--j6w193g nameserver = SEC3.APNIC.NET
xn--j6w193g nameserver = NS3.CUHK.EDU.HK
xn--j6w193g nameserver = ADNS2.BERKELEY.EDU
xn--j6w193g nameserver = NS2.HKIRC.NET.HK
xn--j6w193g nameserver = B.DNS.TW

B.DNS.TW internet address = 210.201.138.58
B.DNS.TW AAAA IPv6 address = 2404:0:10a0::58
NS2.CUHK.EDU.HK internet address = 137.189.6.21
NS2.CUHK.EDU.HK AAAA IPv6 address = 2405:3000:3:60::21
NS3.CUHK.EDU.HK internet address = 202.45.188.39
SEC3.APNIC.NET internet address = 202.12.28.140
SEC3.APNIC.NET AAAA IPv6 address = 2001:dc0:1:0:4777::140
ADNS1.BERKELEY.EDU internet address = 128.32.136.3
ADNS2.BERKELEY.EDU internet address = 128.32.136.14
ADNS2.BERKELEY.EDU AAAA IPv6 address = 2607:f140:ffff:fffe::e
HK-NS.PCH.NET internet address = 204.61.216.46
HK-NS.PCH.NET AAAA IPv6 address = 2001:500:14:6046:ad::1