Ben,

Ok, maybe I'm misunderstanding you.

Why would I need to be port forwarding?

All my relevant hosts and my DNS server all sit on the 192.168 subnet all behind the same firewall with no reason to go near the modem? The DNS server does act as a firewall, but yes, the relevant ports on the eth1 side for DNS are open (namely 53 & for whatever reason - can't remember now - 953).

For clarification the setup is

modem (FW)
    |
Server (FW, DNS, DHCP, etc) eth0 = 10.X subnet eth1 = 192.168 subnet DHCP listens on 192.168.x.x
    |
internal DHCP hosts on 192.168 subnet

------------------------------------------------------------------------
Kind Regards

Kyle


On 15/02/11 1:47 PM, Ben Donohue wrote:
yes that's what I'm talking about.

are you port forwarding DNS to your internal dns server?

setup a test box on the inside of the modem and see if it works with just the modem in place.

Thanks,
Ben Donohue


On 15/02/2011 1:28 PM, Kyle wrote:
 Ben,

thanks for taking the time to look. Perhaps I wasn't clear. My issues are not external clients not updating; rather internal only. I.e. Everything behind my firewalls.

------------------------------------------------------------------------
Kind Regards

Kyle


On 15/02/11 1:11 PM, Ben Donohue wrote:
Hi,

I'd check that you are port forwarding or "virtual server" from the modem port 53 tcp and udp to the internal dns server

reboot everything starting from the modem and working your way inwards

try to simplify the problem. Run up a new box if you can and stick it temporarily on the inside of the modem and see if it is getting dns correctly... go to websites etc.... if working then place it on the other side of the svr1 and test from there...


Thanks,
Ben Donohue


On 15/02/2011 11:59 AM, Kyle wrote:
 Hi SLUG,

I have an issue that is becoming more annoying the more I try to track it down.

Can I ask those of you interested to take a look at the following thread please: https://www.centos.org/modules/newbb/viewtopic.php?topic_id=30080&forum=40

I realise this might be a little .... brave ... to ask you to go outside the list, but it is a fairly detailed thread (i.e. lengthy read) with all the necessary info on the box's config and all the testing I have done.

In short;
-----------
mixed clients XP, 7, OSX, Ubuntu 10 to a CentOS 5.5 svr all in an MS WORKGROUP type setup.
DHCP licences handed out, some reserved.
DNS zones supposedly set up to provide name-based network browsing within the WORKGROUP domain and for internal clients to find inbound mail servers for 5 other domains.
-----------

But try as I might, I can't seem to get the DNS updated anymore and I swear it USED TO WORK. The only thing I have since done is update the packages as they came out.

I am as far as the error: "Unable to add forward map from client1.domain1.com to 192.168.1.104: not authorized" and that's where it stops. No amount of googlage has so far shone a torch on the issue. The disheartening thing is the bloody redmond boxes CAN find other hosts by name, but not the linux or OSX boxes.

If you have the time and incl. to have a read and point out where the hell I'm going wrong pls, I'd be grateful.


--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to