HOME  → POSTS  → 2003

Freakin' DNS and TCP/IP...

Tech Life226 words2 minutes to read

When it comes to networking, I’m still somewhat of a beginner. I understand many of the concepts, can put together a Workgroup or Domain using Windows 2000 Server, and can generally not screw things up too much.

One of the many things that I still don’t understand is what the crap is wrong with our server. I’m trying to get the internet connected to our small domain at work. I’ve got two NIC’s connected to the server: one for the DSL connection, and one for the internal network. I’ve got Network Address Translation enabled and working… more or less.

I can ping the IP of the router from the internal network, which tells me that NAT is working. I can ping the IP for this website from the internal network as well. When I’d gotten that far I got pretty excited. I fired up Mozilla Firebird with giddy glee and saw this:

Screenshot of Google not being found.

The server can get on the internet no problem using domain names, but I can’t. I’m stuck having to ping various websites from the server to get the IP address, and surf the web punching in addresses like and It’s all very irritating.

I know that the problem lies with the server not translating the DNS properly, and that just sucks. I guess it’s back to screaming and swearing at TCP/IP again…

Ryan Parman

is an engineering manager with over 20 years of experience across software development, site reliability engineering, and security. He is the creator of SimplePie and AWS SDK for PHP, patented multifactor-authentication-as-a-service at WePay, defined much of the CI/CD and SRE disciplines at McGraw-Hill Education, and came up with the idea of “serverless, event-driven, responsive functions in the cloud” while at Amazon Web Services in 2010. Ryan's aptly-named blog, , is where he writes about ideas longer than . Ambivert. Curious. Not a coffee drinker.