Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
DNS issue with website from inside network
Posted on 2009-04-02
Hi all,
I am having a very weird issue. My client just had their website moved to another location out on the internet. The OLD ip address of their website was: 207.99.0.121. The NEW address is 66.7.204.76. My client's internal network continues to see: 207.99.0.121
If I manually map the hosts file on the server I can get there. I've checked, rechecked, and checked again through DNS and cannot find an entry for www.domain.com with the old IP, nor do I have one for the new IP. The internal FQDN is natrelusa.local, external domain name is natrelusa.com. I've also just done something as simple as "ipconfig /flushdns /registerdns" and it's good for a few days... then reverts back to the old address.
Any floggin ideas?
Running Websense, PIX firewall, Server 2003.
I am having a very weird issue. My client just had their website moved to another location out on the internet. The OLD ip address of their website was: 207.99.0.121. The NEW address is 66.7.204.76. My client's internal network continues to see: 207.99.0.121
If I manually map the hosts file on the server I can get there. I've checked, rechecked, and checked again through DNS and cannot find an entry for www.domain.com with the old IP, nor do I have one for the new IP. The internal FQDN is natrelusa.local, external domain name is natrelusa.com. I've also just done something as simple as "ipconfig /flushdns /registerdns" and it's good for a few days... then reverts back to the old address.
Any floggin ideas?
Running Websense, PIX firewall, Server 2003.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
2
6 Comments
Hi guys,
I just created another forward lookup server in DNS on my server. I created it natrelusa.com and then gave it a www A record for the proper IP address. I then did a /flushdns /registerdns. This resolved it momentarily (flushing and re-registering, as it has in the past).
Wonder if the new forward lookup server for natrelusa.com will resolve it for good?
I just created another forward lookup server in DNS on my server. I created it natrelusa.com and then gave it a www A record for the proper IP address. I then did a /flushdns /registerdns. This resolved it momentarily (flushing and re-registering, as it has in the past).
Wonder if the new forward lookup server for natrelusa.com will resolve it for good?
Active today
That should fix it for good. There is an issue to be aware of. If the only entry in the external natrelusa.com zone is www, then that's ok. However, if you send email to someone@natrelusa.com, that will fail within the network. The reason for this is that there are no MX records for natrelusa.com on your internal DNS server.
A better fix would be to create a new zone on your internal DNS server and name the zone www.natrelusa.com. Then within that zone, create a blank A record pointing to the appropriate address.
A better fix would be to create a new zone on your internal DNS server and name the zone www.natrelusa.com. Then within that zone, create a blank A record pointing to the appropriate address.
Having no issues sending internal e-mail since I made the change. Do you suggest I make this change now?
Active today
I would change it to what I said earlier just to avoid any problems in the future. If you set it up my way, any requests for anything other than www.natrelusa.com, for example ftp.natrelusa.com will be forwarded to the correct external DNS server.
If you leave it the way you've set it up, any future changes to the external natrelusa.com zone will need to be replicated on the internal natrelusa.com zone otherwise the changes won't work from within the LAN.
If you leave it the way you've set it up, any future changes to the external natrelusa.com zone will need to be replicated on the internal natrelusa.com zone otherwise the changes won't work from within the LAN.
Featured Post
Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums.
I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you!
In this Micro Tutorial, you'll learn yo…
- Microsoft Applications
- Windows 10
- Windows OS
- Fonts Typography
- Windows 7, Microsoft Word
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month6 days, 11 hours left to enroll
636 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.