DNS for the biglose
If you've read through my prior posts, you would most likely have figured out that I work at a computer company, no names mentioned. We "specialize" in, amongst other things, "Connectivity/Network support".
Don't let that fool you though. Last week Monday, whilst on leave, I was called in for an "emergency". We'd supplied a server to handle a company's VPN networking. And for some reason, it wasn't working properly. So that led to me having to drive out to Alberton to sort out the problem.
Upon arriving, I noticed that the computers weren't logging on to the domain server across the VPN. They were XP boxes, and were logging on in offline mode. And for some odd reason, this was a major mindfuck for everyone at my company. The response I received from them was something along the line of, "ZOMGROFIL MICORSOFT HAAAAXXXXX!!@%". Obviously they missed the memo on XP's biggest corporate selling point.
Anyhow, I managed to talk the boss through enabling remote administration on the server, which I could ping through the VPN. And subsequent to that, I logged onto the server, and took a look at the services. Guess what? No DNS server service had been set up. Gee, no wonder the DNS wasn't being broadcast to those machines. No wonder the domain controller wasn't being seen by other ip ranges.
So I set up the DNS, and phoned the engineering manager. After telling him what the problem was, he responded very intellectually, saying, "ROFLMAYOLOLZ BUT TEH PEE SEE R TEH LOGIN 2 TEH DOUGH MAIN!!!1!".
"Yes, I know they are on the one ip range. But there's a difference between DNS server and domain server."
"ROFL IT R LOG ON????"
"No, it's in offline mode."
"ZOMGH4XXX0RRR3D!!!!!!"
At about this point, I tried to change the topic onto that of farewells, since obviously I was the only person that half knew what a DNS server did. I just wanted to get rid of the man and go sleep.
The moral of this story though, is that the only two people in this company that seem to have the foggiest about DNS are sitting in the sales section.
Don't let that fool you though. Last week Monday, whilst on leave, I was called in for an "emergency". We'd supplied a server to handle a company's VPN networking. And for some reason, it wasn't working properly. So that led to me having to drive out to Alberton to sort out the problem.
Upon arriving, I noticed that the computers weren't logging on to the domain server across the VPN. They were XP boxes, and were logging on in offline mode. And for some odd reason, this was a major mindfuck for everyone at my company. The response I received from them was something along the line of, "ZOMGROFIL MICORSOFT HAAAAXXXXX!!@%". Obviously they missed the memo on XP's biggest corporate selling point.
Anyhow, I managed to talk the boss through enabling remote administration on the server, which I could ping through the VPN. And subsequent to that, I logged onto the server, and took a look at the services. Guess what? No DNS server service had been set up. Gee, no wonder the DNS wasn't being broadcast to those machines. No wonder the domain controller wasn't being seen by other ip ranges.
So I set up the DNS, and phoned the engineering manager. After telling him what the problem was, he responded very intellectually, saying, "ROFLMAYOLOLZ BUT TEH PEE SEE R TEH LOGIN 2 TEH DOUGH MAIN!!!1!".
"Yes, I know they are on the one ip range. But there's a difference between DNS server and domain server."
"ROFL IT R LOG ON????"
"No, it's in offline mode."
"ZOMGH4XXX0RRR3D!!!!!!"
At about this point, I tried to change the topic onto that of farewells, since obviously I was the only person that half knew what a DNS server did. I just wanted to get rid of the man and go sleep.
The moral of this story though, is that the only two people in this company that seem to have the foggiest about DNS are sitting in the sales section.
posted by Mburr at
12:06 pm
1 Comments:
So... you cant get a better job... why?
By
Zulu, at 2:39 pm
Post a Comment
<< Home