DNS not resolving to External addresses

[nunzeo]

Our internal domain name is test.com . We have added a few external web sites

http://www.test123.com

&

http://www.testfirst.com.

These sites are out of our network. Do I have to add a new zone called test123 and testfirst or new domain to our internal DNS and then point it to the external IP addresses?

Thanks for any help.

 

[ShackDaddy]

The best thing would be to be able to resolve those addresses on the public network, with your internal DNS server querying the public root servers and getting the response.

If you can't do that, or if the site's DNS records aren't really publically published yet, you can also build a zone file on your internal DNS server for each of those domains and populate it with the records you need. Bear in mind that it won't just be A-records you are creating: you will have to create MX records for those domains if you want any of your users to send mail to those domains.

ShackDaddy

 

[lamsf]

I am trying to configure the DNS so that it can query another DNS server for public network.

How do I do that?
I am using RedHat Linux as my DNS server.

Pls help. Thank you.

 

[ShackDaddy]

Look for a setting called "Forwarders" and configure the external DNS server addresses there.

 

[ShackDaddy]

Or you might need to load a root hints file, if you haven't been able to get any name resolution. I'm not sure whether you are trying to just to regular external name resolution against public servers, or whether you have a particular server that you'd like to handle all your queries for you.

 

[ITPangaeaArchitect]

The trick here...Linux DNS

Not sure how to configure on Linux DNS, but I can tell you this, an AD domain should not be running off from Linux DNS...if banything, the DCs should be running DNS, and if you wish Linux to be the bridge for name resolution to the internet, you configure a forwarder for all other domain names to the IP of your Linux server to forward traffic.

-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+
Sr. Infrastructure Management Analyst
Distributed Systems Engineering
ACS, Inc.

 

[ShackDaddy]

There's no indication that there's an AD network here or that he has any Windows servers.

Do you have an etc/named/root.hint file? And is it populated with entries?

Check your named.conf file and see if there is a line like this in there:

options {
forwarders { 192.168.50.10; 192.168.50.20; } ;

That's how you'd point to some external DNS servers.

ShackDaddy

 

[ITPangaeaArchitect]

that is a good point, i was thinking i was answering this in the win2003 forum



-Brandon Wilson
MCSE00/03, MCSA:Messaging00, MCSA03, A+
Sr. Infrastructure Management Analyst
Distributed Systems Engineering
ACS, Inc.

 

[nunzeo]

I just added a new zone file for test123.com and one for testfirst.com and then added a host record for

http://WWW to

point to the external IP address of each site. That worked just fine. I was going to create a script to edit everyone's host file but this was much easier and this way I can change it in a few seconds if for any reason the public IPs of test123 or testfirst change. Thanks for everyone's help.

Nunzeo