NANOG 66 took place a couple weeks ago. Video’s and presentations are trickling on the Internet. Here are the list of video’s and presentations that I found particularly interesting:

  1. Is IPv6 Really Faster? (Video)|(Presentation PDF)
  2. Move Fast, Unbreak Things! (Video)|(Presentation PDF)
  3. NetOps Coding 101 – Python Intro and Regular Expression Deep Dive (Video)|(Presentation PDF)|(Presentation Files)
  4. NetOps Coding 101 – Python Intro and Regular Expression Deep Dive (Part 2 of 2) (Video)|(Presentation Files)
  5. BGP EVPN in Datacenter and Layer-3 Data Center Interconnect (Video)|(Presentation PDF)
  6. Segment Routing in the Datacenter (Video)|(Presentation PDF)
  7. NetOps Coding 201 – Building Facebook’s FBAR for Network Devices (Video)|(Presentation PDF)|(Presentation Files)

You can see the full list of talks and presentations here.

February 15, 2016

Posted In: BGP, Data Center, DevOps, NANOG, Network DevOps, Network Programmability

Using Ansible to update your Home Dynamic DNS via Rackspace Cloud DNS

Like most home Internet users, my home Internet has a dynamic IP Address. For many years, I used DynDNS to keep a hostname associated to my home Internet, so that I could access my home resources remotely. After DynDNS started charging for the service, I just created a sub-domain off one of the domains that I own. The problem has always been that I would only find out about my IP Address changing after a failed login attempt. Since then, I have created a couple scripts. However, as I go down the Ansible journey, I try to apply the same problems to Ansible to see how it can solve problems. So, I decided to write a playbook to have Ansible automatically update my DNS record as needed.

Here is the playbook:

As you can see it’s pretty straight forward. I define several facts up front, mostly dealing with the Rackspace Cloud DNS Authentication, domain, and hostname settings. Then I run plays to determine what my current IP Address is, what the DNS A record is, comparing the two, then updating the DNS as needed.

It should be simple enough to run the playbook as a cron-job. So far, it works great!

The playbook is available via my github.

January 29, 2016

Posted In: Ansible, DevOps