Dots in a hostname

Yesterday I had a very interesting discussion with our senior administrator.

I was configuring reverse DNS records for our /24 block and I decided to use format - thus if for IP, I pointed reverse DNS (PTR) to

When I got chance to show my work to my senior administrator, he said - It’s wrong to use in a hostname. Too many dots will make DNS resolution very slow (forward - reverse - again forward). And I should have used

A very interesting point (and indeed a confusion!)

At first instance I was totally stunned myself and was thinking same as he said. He is senior admin and knows over a million more things then me and such feelings usually pushes you in case when you believe in someone without checking on facts.

(Disclaimer: No offence to my senior admin. He is a very smart person, and a good friend too).

After a while, I gave it a DEEP thought and discussed with a couple of more friends. I got clear idea about it. 

Let’s understand how will be resolved.Here, first of all dns resolver will query com (root) servers for getting NS delegation of Now as will reply with some NS (let’s call them ns1 & ns2). Next, DNS resolver will query ns1 for and done - it will get back reply with A record - (game over!).  :)

Same thing happens even if we use So what “could have” caused slowdown?

There can be a significant slowdown IF for say in acts as a separate DNS zone rather then acting as nothing (when we create A record for If has separate NS, and assume is a further sub zone defined by some other NS …the one which are different then parent nameservers. But in our case or or is just nothing. The only thing was which was simply an A record on parent domain name.

Hence is same as and I assume it’s rather an issue of convention admins prefer rather then any technical reason behind it.