Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

FQDN (Fully Qualified Domain Name) & DN (Domain Name)

Hello All,

Could you please provide me possible explanations why loading of webpage using FQDN is much much faster than

loading of webpage using DN ?

Traceroute for FQDN and DN is the same --> no routing issue

Thank you,

Jan

2 REPLIES

FQDN (Fully Qualified Domain Name) & DN (Domain Name)

Hi Jan,

I assume you by DN you mean hostname. Using just the DN would default you to a specific host depending on the protocol used: http -> 80 -> www, smtp -> 25 -> mx

This sounds like an issue regarding DNS setup on your machine.

When you search using just the hostname, your machine must add the domain suffix which has been configured on your machine. If this does not produce a result, then it will iterate through the other domains listed under your search domains. It is this iteration that takes time.

By using a FQDN you are providing a precise uniquely identifiable address so it will be quicker to resolve via DNS and access.

If you are using Linux, take a look at /etc/resolv.conf

cheers,

Seb.

New Member

FQDN (Fully Qualified Domain Name) & DN (Domain Name)

Hi,

Domain is used for name resolution. I think an example is the best solution to explain the difference between a Domain Name and FQDN.

If your PC name = A

Your PC's Domain Name = cisco.local

Your FQDN = A. cisco.local

So FQDN is the host name with domain name so that the specific host can be identified easily. Domain name is just the domain under which the PC reside.

Thank you.

* Please rate the helpful posts.

731
Views
1
Helpful
2
Replies
CreatePlease login to create content