Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows domain name query

Status
Not open for further replies.

dsdjnpfvf

IS-IT--Management
Aug 21, 2003
38
GB
Hi,

Our company is about to move to Windows 2003 from NT4 (yes it's taken us a while :) )

I'm curious, I know that Windows 2000 and higher use DNS for the hostname resolution on a network as opposed to the old method of WINS. I'm confused about what to actually call the domain.

Obviously the DNS for my LAN will be holding private IP addresses, i.e 10.x.x.x, and not routable IPs, so surely I shouldn't use my companies internet domain name as the name of the domain, which is wisltd.com. Someone said to me a while ago, that you should always end your LAN domain name in .local, i.e wisltd.local. Is this correct?

Also, since my server will have 2 NICs, one to the internet with a public IP and one to the LAN with a private IP, wouldn't it need two host names? It just seems wrong to me that in the e-mail headers of e-mails sent out from my test setup, it says:

Recieved from win2k3.wisltd.local (81.45.45.x)

Everything works, it just seems that I've got it all wrong with regards to the DNS setup, since it should say

Recieved from mailserver.wisltd.com (81.45.45.x)

In my internet DNS, mailserver.wisltd.com is mapped via an A record and an MX record to the public IP of the server. It sends and recieves fine, just the headers are wrong, and it gives out internal network info in the e-mail headers, which isn't too good.

Any help greatly appreciated,

Daniel Briley




 
Don't worry about the headers on the email... If the server works, it works. If you host your website internally, then you would need a .com (or similar) address marked to your IP but with mail servers, it doesn't matter. The MX record is attached to your IP.

Your friend was right about the .local.

~ K.I.S.S - Don't make it any more complex than it has to be ~
 
So if I was to host my website on the same server, would it matter if the hostname wasn't the same as the DNS name for the website?

This is providing that the internet DNS still points to the public IP of the server.

So am I right in saying that only machines on perimeter networks which are available to the internet and seperate from the internal network should have an actual hostname which is valid on the internet?

Thanks for the help,

Daniel
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top