[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

The Strange DNS issue

Story: We had a project to migrate webserver www.abc.com.au(Melbourne) to our new site in sydney. After finished migration. I added a new forward lookup zone (save the zone in the AD becaseu DNS server in our DC) abc.com.au with a A host recorder *.abc.com.au as the ip 172.xx.xx.xx.  Then i can open webpage from internal to accss our web server. For some reason, i have remove the zone abc.com.au in our DNS because our users need to access the original website in melbourne. Then i delete the zone abc.com.au from Forward lookup zone. The problems are coming:
Problem 1: I can not open the web page of www.abc.com.au (210.xx.xx.xx)in melboune site
                  from my PC because when i type www.abc.com.au in my IE browsers, the web
                  page still come from the internal web server in sdyney (172.xx.xx.xx).
              2: but i can use IE browser to open web page of www.abc.com.au (210.xx.xx.xx) in
                  DC.
              3: nslookup www.abc.com.au from my pc, i can see the ip is (210.xx.xx.xx), even i
                  ping www.abc.com.au, the ip is 210.xx.xx.xx

So, is there some one can tell me why? and how can i fix the problem in DNS? Is it dns replication problem?
           
0
michaelit
Asked:
michaelit
  • 2
  • 2
1 Solution
 
Jaymz_RCommented:
not sure if you have restarted the computer

but you need to perform

ipconfig /flushdns

on both server and machine ... wait 1 minute, then go to the website
0
 
michaelitAuthor Commented:
Hi Jaymz,
   Actually i tried to restart the pc and perform ipconfig/flushdns, but still the same problems. not only my pc, all pcs in internal network has the same problems. I think the zone or A record in DNS was not deleted completely, but i arleady check the DNS, cannot find any more about our new web server record.
0
 
SteveNetwork ManagerCommented:
what about your routers and switches ? have you cleared arp tables ?

you've changed IP's so always best practice to clear arp..
0
 
michaelitAuthor Commented:
Hi All,
   Now it is ok by DNS itself, but it take very long time. So do you guys think it is becasue the DNS or AD laytance problem?
0
 
Jaymz_RCommented:
couldn't tell you truthfully.  Could be an AD Replication problem.  could be a number of problems.  1 positive thing.  its fixed :)
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now