After some use I’ve notice that it’s breaking a lot of stuff, including YouTube and feeds from ArsTechnica.

I’ve looked a bit dipper and it looks like only www.l.google.com has IPv6 working. To make things easier, I’ve dropped whole google.com and google.co.uk zones. Instead I’ve created a zone for www.l.google.com only.

zone "www.l.google.com" IN {
type master;
file "pri/db.www.l.google.com";
notify no;
};

Which contains :

$TTL    86400
@       IN      SOA     ns1.yllq.net. seeder.mobygeek.net. (
2009040101      ; Serial
604800         ; Refresh
86400         ; Retry
2419200         ; Expire
86400 )       ; Negative Cache TTL
;
@    IN    NS    ns1.yllq.net.
@     IN AAAA 2001:4860:a003::68
*     IN AAAA 2001:4860:a003::68

Just to make sure

All what can, runs via IPv6 , everything else is going via IPv4.

Now when you are using your own DNS server you are in disadvantage.

So to have *.google.com and *.google.co.uk I have created zones on my server using IPv6 address from ipv6.google.com . I have not included IPv4 address as well … I don’t need it, I’m full IPv6 here.

You may also consider adding zone for your language/national google domain like google.pl for polish.

Full article has configuration snippets used by me with my BIND server . Click More…

First we need to create zone file, mine is pri/db.google.com and pri/db.google.co.uk

this is what is inside :

$TTL    86400
@       IN      SOA     ns1.yllq.net. seeder.mobygeek.net. (
2009032901      ; Serial
604800         ; Refresh
86400         ; Retry
2419200         ; Expire
86400 )       ; Negative Cache TTL
;
@       IN      NS      ns1.yllq.net.
@               10800   IN      MX      10 smtp1.google.com.
@               10800   IN      MX      10 smtp2.google.com.
@               10800   IN      MX      10 smtp3.google.com.
@               10800   IN      MX      10 smtp4.google.com.

*       IN AAAA 2001:4860:a003::68

smtp1.google.com.       3600    IN      A       209.85.237.25
smtp2.google.com.       3600    IN      A       64.233.165.25
smtp3.google.com.       3600    IN      A       64.233.183.25
smtp4.google.com.       3600    IN      A       72.14.221.25
ns1.google.com.         9600    IN      A       216.239.32.10
ns2.google.com.         9600    IN      A       216.239.34.10
ns3.google.com.         9600    IN      A       216.239.36.10
ns4.google.com.         9600    IN      A       216.239.38.10

now we have to configure bind to include them , in my case I have my zones split into internal and external views so this lands in view accessible by internal systems only :

zone "google.com" IN {
type master;
file "pri/db.google.com";
notify no;
};
zone "google.co.uk" IN {
type master;
file "pri/db.google.co.uk";
notify no;
};

Now simple restart of the named ( or rndc reload ) should bring IPv6 *.google.com to you. It did for me.

You may want to add A record for IPv4 only clients, put that after the AAAA record :

*        300    IN    A    74.125.45.100
*        300    IN    A    209.85.171.100
*        300    IN    A    74.125.67.100

Enjoy google on IPv6, comments welcome.

Some more of Randolph Lalonde

I’ve bought the FirstLight – Omnibus and as Spinwardfringe, it kept me glued to the screen. I really like your work, keep them coming! You can get Freeground on Amazon now.

Some more of coding

I am currently writing brand new munin plugin for Bind using stats output. I had some experience with plotting bind but none of the old ones works with my system so I am writing my own.

Some more cursing

Backup Exec and Windows server – why this shit doesn’t want to backup local resources ?!

Now you wish to connect to one of the servers. You are typing

ssh mylovelyserver.somesubdomain.mylovelylongdomain.tld

How much do you like to type such a long address ?

When you are working from one machine, you can set it up, so you can very easy access your servers.

You can use

search somesubdomain.mylovelylongdomain.tld

or

domain somesubdomain.mylovelylongdomain.tld

in your

/etc/resolv.conf

which make your servers accessible just by the host name. Then

ssh mylovelyserver

does the job.When you are feeling really lazy, you can setup some aliases in your shells rc file. Something like

alias ssh-mylove = ssh mylovelyserver.somesubdomain.mylovelylongdomain.tld

can save a few key strokes.That was easy when you were working from the same computer all the time. It would be even easy if you would work from a few computers, where you keep your configurations synchronized.

It is not so easy when you have to connect to your servers from different locations and systems which you are not in control of. You are back to typing all that lovely.nice.descriptive.domain.names.

That is why I am opting for a short, not descriptive, easy to type domain names. Which you will use for fast access. Typing

ssh sharp.yllq.net

is much quicker than

ssh sharp.somesubdomain.mylovelylongdomain.tld

Have you tried to dictate yours servers domain location over the phone ? I do it quite often, and believe me, even it the domains make sense for you, they might be confusing for people and longer domains are asking for more mistakes. it is easier to say s-h-a-r-p.y-l-l-q.n-e-t than s-h-a-r-p.s-o-m-e-s-u-b-d-o-m-a-i-n.m-y-l-o-v-e-l-y-l-o-n-g-d-o-m-a-i-n.tld just to make sure person at the other end of the phone got it right.