> > I want to be sure I understand this name resolution process > while running > dnscache and tinydns. When loaded, dnscache looks for any > name resolution > queries and, when caught, resolves these by checking the > content of the > tinydns private or public zone files depending on the origin > of the name > resolution query. Is that correct? > > How does MaraDNS function under Dachstein? dnscache isn't > running under the > maradns configuration. >
Found the problem- in the mararc config file, maradns bounded itself to ip address 192.168.1.254 but I had set the router's DNS resolver address as 127.0.0.1. Once I reset the DNS resolver address for the router to 192.168.1.254, I was able to ping internal and external hosts from the router. Lesson learned. As a side note, the webmaster of www.dawnsign.com confirmed that it isn't set to respond to pings. Seems it's quite common among web hosting servers not to respond to pings in an effort to reduce traffic. Ummm. On to the next problem! ~Doug ------------------------------------------------------- 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
