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
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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.
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.
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.
Business Accounts
Answer for Membership
by: dariusgPosted on 2009-04-20 at 09:40:31ID: 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.