?
Solved

Removing DNS settings from Server 2003

Posted on 2009-04-20
6
Medium Priority
?
254 Views
Last Modified: 2012-06-21
I have recently moved a client from Exchange Server 2003 to Corporate Gmail. There are DNS settings that catch any traffic leaving the internal network going to our "domain".com and routes it back to 192.168.1.253(the primary server). I'm trying to remove this routing, but don't want to screw anything up. I've located the files there, but don't want to just go through deleting everything. Can someone please inform me of anything else that these rules may do besides redirect these connections?

Thanks,

Chris
0
Comment
Question by:pccbryan
  • 3
  • 3
6 Comments
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 24186216
You shouldn't have any problems just deleting the record but if you are concerned then make a backup of DNS or write down the settings for this record. To be honest the only way to find if it is going yo screw anything up is to remove it. This won't mess any Network Infrastructure services up but if you have a website on your local domain that is located at this address you might lose connectivity to it until you place the record back in.
0
 

Author Comment

by:pccbryan
ID: 24247046
Ok. I paused the current domains that are controlled by the DNS server. Once I did that I flushed the DNS cache on a workstation and tried to ping the domain I'm trying to reach. It gave me a host cannot be reached message.

I'm really at a loss here on what to do. Any other suggestions.

No local website to worry with, I do have a printer that is emailing scans out to mail.domain.com. That is why we are trying to resolve this issue.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 24255350
If the domains are paused then you will have issues. You should just delete the record but make sure you have a backup of the information.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:pccbryan
ID: 24255428
I unfortunately did not have any more time to play with it. I changed the DNS server at the workstation level to bypass the DNS Server and point to an outside DNS server provided by my ISP. This worked. It wasn't the solution I was hoping for... but it was the first thing that I found met my needs.

I will leave this open for a day longer for any other suggestions because I'm not satisfied by the solution I had to come up with.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 24255477
If you are on a domain environment then you need to remove the ISP DNS server from the workstation because the workstation can't speak to the local DNS server.

Again just remove the record from DNS. Point the client to the DNS server. Make sure the DNS forwarders on the DNS server are up to date. If the DNS zones are paused and the client is pointed to them then the client won't be able to resolve any DNS.
0
 

Accepted Solution

by:
pccbryan earned 0 total points
ID: 24358089
I ended up just bypassing the DNS server at the workstation level. It wasn't at all the solution that I was hoping for... but it did the job. I pointed it directly to an openDNS server.

0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question