have accidently named the internal domain tuna.net rather than tuna.lan or .local. what are the implications for DNS, Exchange, active directories etc > Small Business Server Support Forum

Unanswered Active Topics

Forums Search

Forums > Microsoft Small Business Server 2003 & 2000 > Exchange Server 2000

Subject: have accidently named the internal domain tuna.net rather than tuna.lan or .local. what are the implications for DNS, Exchange, active directories etc

Prev Next

You are not authorized to post a reply.

Author

Messages

David Bell User is Offline

Australia
Member since
5/19/2007

Registered Users
Posts: 8

5/19/2007 06:04 AM
Hi all, mean't to type DomainName.lan for the local domain and accidentally typed Domainname.net (eg companyname.net). What problems may I have, if any with DNS, Exchange, ActiveDirectories etc as a result. What can I do to fix the situation if need be (I don't wish to reinstall). The company hasn't purchased a public domain name as yet but would be looking at companyname.com. Again what are the implications at this stage. Merlin

Mariette Knap User is Online

The Netherlands
Member since
3/24/2005

Forum Admins
Posts: 12959

5/19/2007 08:36 AM

Whipe the box and reinstall.

Mariëtte Knap Smallbizserver.Net Administrator

Mission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'

Eriq Neale User is Offline

Texas, USA
Member since
5/3/2005

Microsoft MVP
Posts: 2117

5/19/2007 02:55 PM
David - There are not going to be any performance issues internally to the server, Active Directory, or the workstations. The only hiccup you may encounter is if you find that you're needing to access public resources that exist in the domainame.net DNS namespace. Does this namespace already exist? If not, I'd recommend purchasing it and then leaving it completely unused to prevent any future problems for public networking. But there is not anytying inherently evil about using a publicly-routable domain name internally. One of my early server installs was done with a domain.com internal namespace, and it's humming along just fine. The only extra work I've had to do is enter public site names with their public IP addresses in the internal DNS configuration of the server, but as the domain is fairly static, it's not been an issue. If you're not too far down the road, and you're really concerned about it, go ahead and rebuild the box. But if that public domain name is not currently registered, or you don't expect that anyone in the company woudl need to access resources in that domain, it's probably not going to be a headache for you. HTH... -Eriq

Eriq Neale - Small Business Specialist, SBS MVP, Mac Guru EON Consulting LLC www.eonconsulting.net Lead Author of Windows Small Business Server 2008 Unleashed In bookstores December 10, available for pre-order now Listen to eOnCall at AIRtunZ or visit www.eoncall.com.

David Bell User is Offline

Australia
Member since
5/19/2007

Registered Users
Posts: 8

5/19/2007 03:59 PM
Merlin again... thanks Eriq and Mariette. There is public domain carrying the same domain as my internal - say coldfish.net. Remember I had planned to type .lan but accidently typed .net - it happens!! The only problem I am experiencing is a 4.4.7 email delivery error when sending email. There appears to be a DNS problem maybe reverse DNS lookup. some mail appears to be getting through. Can this error possibly be the link/fault. I'm desperate... regards Merlin

Eriq Neale User is Offline

Texas, USA
Member since
5/3/2005

Microsoft MVP
Posts: 2117

5/19/2007 04:04 PM
David - Would need more information or access to the box to troubleshoot further. If you could post the entire contents of the 4.4.7 NDR in a private message I can see if that gives any information. Outbound mail delivery doesn't care what your internal domain is. In all likelihood, there's something else going on. -Eriq

Eriq Neale - Small Business Specialist, SBS MVP, Mac Guru EON Consulting LLC www.eonconsulting.net Lead Author of Windows Small Business Server 2008 Unleashed In bookstores December 10, available for pre-order now Listen to eOnCall at AIRtunZ or visit www.eoncall.com.

David Bell User is Offline

Australia
Member since
5/19/2007

Registered Users
Posts: 8

5/22/2007 11:42 AM
Hii all, I solved this problem relating to the send error from exchange and the 4.4.7 response. Interestingling the logs looked great. I went into internet and email wizard, accepted the defaults which were fine eg router details, server external lan card details, server internal lan card details etc. When I got to the sent email resolution dialogue box, I changed the setting from let DNS do it, to forward exchange mailbox to ISP mailbox and use this to send the mail (I'm doing this from memory). There is one last issue though, when you receive a message from the sender in the server domain, you can't reply to the message as the local email address is in the reply-to part of the message eg tom@lambchops.net or tom@lambchops.local , remember I typed .net instead of .lan (by accident). thnkyou for your help regards merlin

You are not authorized to post a reply.

Forums > Microsoft Small Business Server 2003 & 2000 > Exchange Server 2000 > have accidently named the internal domain tuna.net rather than tuna.lan or .local. what are the implications for DNS, Exchange, active directories etc

ActiveForums 3.7