Topic: help!! i cant surf, keep gettin lame server resolving error

[nef kho]

hi, anyone can help me explain with my error log message, i have sme56, dialup with statitic ip. i get this ff. error:

Apr 23 06:18:45 e-smith named[2973]: lame server resolving 'www.e-smith.dyndns.org.xxx' (in '.'?): 192.203.230.10#53
Apr 23 06:18:45 e-smith named[2973]: lame server resolving 'www.e-smith.dyndns.org.xxx' (in '.'?): 198.41.0.10#53
Apr 23 06:18:45 e-smith named[2973]: lame server resolving 'www.e-smith.dyndns.org.xxx' (in '.'?): 198.41.0.4#53

thanks,

nef

[Jesper Holck]

Do you get this exact message all the time? Including the "xxx"?

[nef kho]

yes, the messages is a copy of the error log, did not modify or change anything, what do you think is wrong?

thanks

[nef kho]

hi, i tried changing the named.conf with the following forwaders:

#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# SME Server software. Instead, modify the source template in
# an /etc/e-smith/templates-custom directory. For more
# information, see http://www.e-smith.org/custom/
#
# copyright (C) 2002 Mitel Networks Corporation
#------------------------------------------------------------



options {
   directory "/var/named";
        forward first;
   
   forwarders { 210.23.234.33; 210.23.234.65; };  
   
   
   listen-on { 127.0.0.1; 192.168.0.33; };
   /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below.  Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
   // query-source address * port 53;
};
#----------------------------------------
# root name servers
#----------------------------------------

zone "." {
   type hint;
   file "named.ca";
};
#----------------------------------------
# localhost PTR record
#----------------------------------------

zone "0.0.127.in-addr.arpa" {
   type master;
   file "named.local";
};

zone "localhost." {
   type master;
   file "named.localhost";
};
#----------------------------------------
# local network PTR records
#----------------------------------------

zone "0.168.192.in-addr.arpa."
{
   type forward;
   forward first;
   
   forwarders { 210.23.234.33; 210.23.234.65; };
};

zone "fortunesea.com.ph"
{
    type forward;
    forward first;
   
    forwarders { 210.23.234.33; 210.23.234.65; };
   
};

---------------------------------

how will i make a custom templates for this? sorry i havnt done any custom template yet and i tried doing but it just dosnt work.

thanks

[nef kho]

hi, i also forgot to mention that with the named.conf setting having forwarders { 210.23.234.33; 210.23.234.65; }; i cant access email using mail.host.com but i can use local ip of the sme.

[Charlie Brady]

nef kho wrote:

> hi, i tried changing the named.conf with the following
> forwaders:
...
> zone "0.168.192.in-addr.arpa."
> {
>    type forward;
>    forward first;
>    
>    forwarders { 210.23.234.33; 210.23.234.65; };
> };

Your changes would seem to be very unwise. Why do you expect the name servers at 210.23.234.33 and 210.23.234.65 to know anything about the names of hosts on your local network?

Why are you using forwarders at all? And where is the "xxx" coming from in your lame server messages?

Charlie

[nef kho]

i got the forwarders and format from my previous e-smith 4 version named.conf which was working ok, the forwarder ip is my isp primary dns and secondary, i think the xxx is from my win98 (tcp/ip -> dns configuration -> host/domain) where i just place xxx/xxx on all workstation.

what i have is a dialup with static ip, i want a sme56 server&gateway mode and my isp gave me primary and seconday dns, when i configure sme56 with out the Master DNS, our email and web hosting is ok locally, but i still get the lame sever problem if the email goes out to other host or if i surf. if i place the Master DNS with the isp primary dns, i cant do email at all using the mail.host.com.

does the problem got to do with my isp?

thanks

here is my current and sme configured named.conf:

----------------------------------------
options {
   directory "/var/named";

   listen-on { 127.0.0.1; 192.168.0.33; };
   /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below.  Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
   // query-source address * port 53;
};
#----------------------------------------
# root name servers
#----------------------------------------

zone "." {
   type hint;
   file "named.ca";
};
#----------------------------------------
# localhost PTR record
#----------------------------------------

zone "0.0.127.in-addr.arpa" {
   type master;
   file "named.local";
};

zone "localhost." {
   type master;
   file "named.localhost";
};
#----------------------------------------
# local network PTR records
#----------------------------------------

zone "0.168.192.in-addr.arpa."
{
   type master;
   file "named.localnetwork";
};

zone "fortunesea.com.ph"
{
    type master;
    file "db.fortunesea.com.ph";
};

-----------------------------------------

[Damien Curtain]

It would easy to be mislead into doing this by the e-smith templates at any rate.

If you add the properties Forwarder[12] to the configuration for the named service, which is valid to do, and then reconfigure named via the event, it will do the exact same thing.

It's not abnormal to use your isp's dns servers as forwarders, where the template systems breaks this is where it attempts to use forwarding for domains where the server is the master, in fragments 40localptrs and 60domains.

The only reason why you would forward these is if you had another dns server on the same subnet, but then you'd configure this server as a secondary anyway. You wouldn't forward for domains where your acting as a master...

If you make a custom template:
/etc/e-smith/templates-custom/etc/named.conf/60domains
{
    my $type = "master";

    foreach my $domain ( @domains )
    {
        my $file = qq(file "db.$domain";);

        $OUT .= <
zone "$domain"
{
    type $type;
    $file
};
HERE
    }
}

and another custom template:
/etc/e-smith/templates-custom/etc/named.conf/40localptrs
#----------------------------------------
# local network PTR records
#----------------------------------------

zone "{ esmith::util::computeLocalNetworkReversed ($LocalIP, $LocalNetmask) }"
\{
{
        $OUT =  "\ttype master;\n";
        $OUT .= qq(\tfile "named.localnetwork";);
}
\};

Then add your ISP's dns servers via the command:
/sbin/e-smith/db configuration setprop named Forwarder1 Forwarder2

Then run the command:
/etc/e-smith/events/actions/named-conf

It should then enable those servers as forwarders yet retain the local server as the master for your locally defined domains.
--
 Damien

[nef kho]

Damien, after following your procedure it's workin already, thanks all. there is still a minor error in log file:

Apr 24 20:10:57 e-smith kernel: PPP: VJ decompression error
Apr 24 20:11:37 e-smith kernel: PPP: VJ decompression error

nef kho