DNS setup

[abovebrd]

I am setting up DNS on my local network. Currently I am using MS wins (yuck) My question is this : Since my internet domain is hosted by my ISP and I will host my local DNS, does it make since to use the same domain name in both DNS setups ie.. My internal DNS server will not be an Authority for the internet domain

sampledomain.com

My internal DNS will only be used for internal name resoloution and will not be an Authority for my internet domain.

I could see how it may cause a problem if they are the same? But maybe not ?

I could use some input

-Danny

 

[Gibson]

I just helped someone solve this exact dilemma today. The answer is a qualified "yes, it can matter." Unless you do a zone transfer and take the DNS tables as they exist right now at your ISP and put them onto your machine, your users may have troubles reaching your own externally-hosted services (like FTP, MAIL &

http://WWW).

Say you are somedomain.com, with a real DNS (ie Authoritative at an ISP) with entires for

http://www.somedomain.com,

ftp.somedomain.com and mail.somedomain.com. These all work fine over the Net. Then, you setup DNS in your building on private IP spaces, like the 192.168.0.0 block. In your "private DNS," which is accessible only to your employees, you point to machines like your NT server, your SCO server, your AS/400, your HP LaserJets, etc., so that in-house people can refer to machines by name only. This is all great until someone tries to go to your public web page at

http://www.somedomain.com,

only to find the in-house DNS isn't up-to-date and they get a wrong page, or a page on an internal server that they mistake for the real publically-accessible page.
My suggestion is to setup your in-house DNS as "somedomain.loc," as in "local." That way, they can still find machines by name, but it won't affect your private perspective on the publically available somedomain.com.
Hope this helps.
Gibson in Nashville

 

[abovebrd]

Thanks Gibson,

Thats what I needed to know



-Danny