Routing problem/ DNS solution

Sherrett O. Walker buznakka at yahoo.com
Thu Jan 19 02:53:58 UTC 2006


Hello, all.

I'm using a Cisco 2600 router in front of a bunch of RHEL servers and a 
bunch of XP laptops and desktops, and I'm having trouble routing 
internal packages using fully qualified domain names to local destinations.
e.g.  foo.example.com from internal brings me an error page.  I've tried 
to work around this by setting up an internal dns server using bind 9 to 
direct everything from inside to the proper ip address- that is, the A 
NAME record of foo.example.com is 34.23.32.23 in my bind configuration.  
This works... to an extent.  It appears that my internal settings take 
precedent for every *.example.com address, even the ones I did not set 
up in my bind configuration.  So, externalmachine.example.com fails 
because my configuration doesn't do what I call a "rollover" to the 
externalnameserver.atmyhost.com (which bind makes you specify).

So, I have a few questions.

Have you had similar problems with such a Cisco Router?
Is this a common workaround?
Why doesn't my "external" authoritative nameserver take care of requests 
to externalmachine.example.com the way it does for espn.com? 
Is there a way I can tell bind that my internal nameserver is allowed to 
look elsewhere for internal  name/ip matching?

I'll direct you to the page from which I took my bind configuration 
guidance: http://www.madboa.com/geek/soho-bind/

Thanks in advance. 
SOW




More information about the redhat-list mailing list