Pointing to external IP from local DNS server

Not sure the title spells it out correctly but here's my problem...

     My local domain is "cool.org" and my web routable domain is "bogus.org". We have a couple of subnets here 10.5.1.x and 10.7.1.x, all of our data machines sit on the .5 subnet, and our phone system machines sit on the .7 subnet.
     One of the phone system's machine is an appliance for conference calling which sits at 10.7.1.8, that machine has to have a DNS record attached to it, so both people from inside and outside of the company can get to it easily, from the outside it's easy enough we just pointed a sub domain host "test.bogus.org" dns record to our WAN ip adress and then forwarded the packets to 10.7.1.8, from the inside, obviously, we didn't want to go out to the web to come back in, so I created a forward/backward looking zone on the DNS server to point "test.domain.bogus" internally, which all works very well.
    So now from the outside if people ping "test.domain.bogus" they see our external WAN address, and from inside they see the local 10.7.1.8. Good!
     The only problem is that "domain.bogus" is actually used outside to forward www. requests to one of our partners sites, which work from the outside world just fine, but within my network it doesn't, obviously, because I have the "domain.bogus" forward looking zone but no records for the www. portion, just the sub domain "test.bogus.org"
    So this should be easy enough, I just need when people from within my network try to go to www.bogus,com to actually get there, right now if you try to ping it you just get: "Ping request could not find host www.bogus.com", again obviously because there are no such records on my local DNS server and the requests dies there as there is a "bogus.org" forward looking zone, but hell if I can figure out how to do that! I created an A host record for "www." (with the right outside IP adress) and then a backward zone for the external IP as well, but no go.
     I know I'm missing something really easy here!
LVL 1
Marvio_SantosAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nick RhodeIT DirectorCommented:
so you added a www record for the bogus.com zone which points to the external IP address of bogus.com.  Did you refresh DNS, on the client side did you perhaps try doing these commands and test again.

ipconfig /flushdns
ipconfig /registerdns
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NumbidCommented:
Or flush cache on DNS server ?

Windows :

Dnscmd ServerName /clearcache

Open in new window

0
Marvio_SantosAuthor Commented:
Nrhode,

Not even kidding you man, 2 minutes after I posted this I figured it out! :) I was complicating thing a bit too much, basically the backward looking zone was confusing the DNS server, I just deleted that and kept the WWW. record and everything worked :) I'll give you the points though...
0
Nick RhodeIT DirectorCommented:
Glad you got it working!!

:)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.