Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > How To Resolve PUBLIC FQDN to INTERNAL PRIVATE IP address

Reply
Thread Tools Display Modes

How To Resolve PUBLIC FQDN to INTERNAL PRIVATE IP address

 
 
Joe Murphy
Guest
Posts: n/a

 
      07-24-2009
Greetings!

I have a situation where I have a Linux box which is not part of AD. It
hosts a web-site and has a FQDN. I do 1 to 1 NAT through my firewall, so
this machine has a private IP address internally, but all web requests from
the public network are forwarded to it just fine.

The problem comes in when workstations that are on the LAN try to get to it.
If I go to a workstation and put in the private IP of the Linux box (e.g.
10.1.3.100) in a web-browser, then it finds the Linux box with no problem at
all. However, if I try to put in the FQDN (e.g. www.linuxbox.com) or the
public IP address, then the web page never comes up and eventually it just
times out.

What I'd like to do is to put an entry into my Server 2003 DNS server that
will route all internal traffic that's trying to get to the FQDN back to the
Linux box's private IP address. Thus far I've had no luck.

Is this something that's doable? There is no entry for the box, as it isn't
part of the AD... I'm a little stuck at trying to add entries that aren't in
the AD.

Any help is MOST appreciated!

Joe


 
Reply With Quote
 
 
 
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      07-24-2009
Hello Joe,

Creating an A record named www with the ip address of the webserver should
help.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Greetings!
>
> I have a situation where I have a Linux box which is not part of AD.
> It hosts a web-site and has a FQDN. I do 1 to 1 NAT through my
> firewall, so this machine has a private IP address internally, but all
> web requests from the public network are forwarded to it just fine.
>
> The problem comes in when workstations that are on the LAN try to get
> to it. If I go to a workstation and put in the private IP of the Linux
> box (e.g. 10.1.3.100) in a web-browser, then it finds the Linux box
> with no problem at all. However, if I try to put in the FQDN (e.g.
> www.linuxbox.com) or the public IP address, then the web page never
> comes up and eventually it just times out.
>
> What I'd like to do is to put an entry into my Server 2003 DNS server
> that will route all internal traffic that's trying to get to the FQDN
> back to the Linux box's private IP address. Thus far I've had no
> luck.
>
> Is this something that's doable? There is no entry for the box, as it
> isn't part of the AD... I'm a little stuck at trying to add entries
> that aren't in the AD.
>
> Any help is MOST appreciated!
>
> Joe
>



 
Reply With Quote
 
Joe Murphy
Guest
Posts: n/a

 
      07-25-2009
As I'm somewhat of a neophyte in this area, could you flesh out some more
detail about how to do what you said for me?

Danke,

Joe


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news: .com...
> Hello Joe,
>
> Creating an A record named www with the ip address of the webserver should
> help.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Greetings!
>>
>> I have a situation where I have a Linux box which is not part of AD.
>> It hosts a web-site and has a FQDN. I do 1 to 1 NAT through my
>> firewall, so this machine has a private IP address internally, but all
>> web requests from the public network are forwarded to it just fine.
>>
>> The problem comes in when workstations that are on the LAN try to get
>> to it. If I go to a workstation and put in the private IP of the Linux
>> box (e.g. 10.1.3.100) in a web-browser, then it finds the Linux box
>> with no problem at all. However, if I try to put in the FQDN (e.g.
>> www.linuxbox.com) or the public IP address, then the web page never
>> comes up and eventually it just times out.
>>
>> What I'd like to do is to put an entry into my Server 2003 DNS server
>> that will route all internal traffic that's trying to get to the FQDN
>> back to the Linux box's private IP address. Thus far I've had no
>> luck.
>>
>> Is this something that's doable? There is no entry for the box, as it
>> isn't part of the AD... I'm a little stuck at trying to add entries
>> that aren't in the AD.
>>
>> Any help is MOST appreciated!
>>
>> Joe
>>

>
>



 
Reply With Quote
 
Meinolf Weber [MVP-DS]
Guest
Posts: n/a

 
      07-26-2009
Hello Joe,

In DNS management console open your forward lookup zone, righclick and choose
new host and type as name www and the ip address of your internal webserver
ip address.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> As I'm somewhat of a neophyte in this area, could you flesh out some
> more detail about how to do what you said for me?
>
> Danke,
>
> Joe
>
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news: .com...
>
>> Hello Joe,
>>
>> Creating an A record named www with the ip address of the webserver
>> should help.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Greetings!
>>>
>>> I have a situation where I have a Linux box which is not part of AD.
>>> It hosts a web-site and has a FQDN. I do 1 to 1 NAT through my
>>> firewall, so this machine has a private IP address internally, but
>>> all web requests from the public network are forwarded to it just
>>> fine.
>>>
>>> The problem comes in when workstations that are on the LAN try to
>>> get to it. If I go to a workstation and put in the private IP of the
>>> Linux box (e.g. 10.1.3.100) in a web-browser, then it finds the
>>> Linux box with no problem at all. However, if I try to put in the
>>> FQDN (e.g. www.linuxbox.com) or the public IP address, then the web
>>> page never comes up and eventually it just times out.
>>>
>>> What I'd like to do is to put an entry into my Server 2003 DNS
>>> server that will route all internal traffic that's trying to get to
>>> the FQDN back to the Linux box's private IP address. Thus far I've
>>> had no luck.
>>>
>>> Is this something that's doable? There is no entry for the box, as
>>> it isn't part of the AD... I'm a little stuck at trying to add
>>> entries that aren't in the AD.
>>>
>>> Any help is MOST appreciated!
>>>
>>> Joe
>>>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can resolve by hostname, but not with FQDN (internal and external) Foes DNS Server 4 03-17-2009 11:09 PM
Best Practice to keep Public & Private IP Address insidematrix Windows Server 2 06-07-2006 01:51 PM
Re: public FQDN resolves to private IP Kevin D. Goodknecht Sr. [MVP] DNS Server 2 07-28-2005 02:18 PM
Re: public FQDN resolves to private IP Steve Duff [MVP] DNS Server 2 07-28-2005 05:28 AM
DNS won't resolve public domain url's that have same root as private Windows Domain Roger DNS Server 3 04-24-2004 10:17 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59