I finally got around to replacing TinyDNS with MaraDNS. The clients are able to resolve names but the router itself isn't able to resolve two names- or at least it does but then isn't able to ping these two addresses successfully.
Network schematic:
Internet <---> DCD router <---> internal network
Here's what I did:
took out references to dnscache and tinydns and replaced these with maradns- pointing to the .lrp package on the floppy. updated the mararc file with what I believe to be appropriate changes.
<snipped file contents>
Now, when I ping www.dawnsign.com I see that my request resolves to an IP address of 207.158.59.34 but then it drops dead announcing it is unable to reach the host. The same thing occurs if I try to ping www.dawnsignpress.com which is under our control as well. We use easyDNS to manage our external domain names and hosts records. When I attempt to ping internal hosts from the DCD router, it does not resolve- instead it announces the internal host as an unknown host. However, when I ping internal hosts from an client inside the internal network, it resolves correctly.
I had hoped that the router would use its own zone file but I might not be thinking correctly. At least MaraDNS appears to behave differently from tinyDNS which had it's internal and external zone files.
If anyone could enlighten me on this subject, I would be grateful. Especially if there is a method where the router could resolve its own queries for internal hosts. I also apologize for this lengthy post.
I'm not familiar with MaraDNS, but I can think of at least two possible problems you could be having. The first is the DNS configuration of your router. You need to make sure the router is setup to use itself as a DNS server if you're running a name server on the router. It's possible your internal systems are properly querying the router for DNS info, while your router is still querying your ISP, which may (but probably does not) have correct DNS info for your local domain.
The other potential problem is hinted at by your indication that www.dawsign.com resolves to 207.158.59.34 (a public IP). If you're port-forwarding from your routers external IP (purely speculation on my part), or otherwise doing some form of NAT, masquerading, or other manipulation of the IP address portion of traffic between the system running your website and the internet in general, you typically have to present different IP's to querying hosts, depending on where they are located. For instance, your internal systems and the firewall should probably access the internal (and likely private IP) address of your web server. Systems on the internet in general (ie connecting via your upstream link) should be given the public IP of your firewall. The interaction with firewall rules you may (or may not) have in place gives three major "zones": the external internet, your internal network(s), and the firewall itself. A problem with the IP address presented by DNS, particulars of your port-forwarding/NAT/MASQ/etc setup, and IP Chains rules currently in place all affect whether everything works properly from each of the three major "zones".
Since you didn't provide anything but the MaraDNS setup (which I'm not familiar with, so pretty much skipped over), I can't help with more specifics. If the above isn't enough to help you figure out whats causing the problem (assuming it's not fundamentally a MaraDNS problem), please post the complete output of "net ipfilter list", along with the exact ping results from both your firewall and an internal system. A general overview, discussing how you're trying to setup access to your public webserver would help as well.
-- Charles Steinkuehler [EMAIL PROTECTED]
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
