References: <200302211757.MAA28047@kasumi.vipnet.org>
Restarting named can be done in multiple ways depending on your OS
and/or the version of bind you are running;
cd /etc/init.d; ./named restart
ndc reload or rndc reload
service named restart
The last one is available in redhat linux, but I am not sure what
other operating systems do this. The ndc vs. rndc are bind specific.
Tinkering with /etc/resolv.conf should only be done if you know it
will not impact other users/domains hosted by that server. On the
other hand, I have never seen a resolv.conf that did not have either
a "domain" or "search" statement, even in a hosted situation. This
is probably a contributor to your problem.
As for sendmail, the same story goes. If the same binary and it's
config (sendmail.cf) is used for just your domain or for multiples,
it would not be wise to just reload it outside a normal maintenance
window. Regardless, I would not restart sendmail until the dns (named)
is corrected/restarted. Sendmail does have a dependency on this as
well. Sendmail is restarted in a similar manner to named;
cd /etc/init.d; ./sendmail restart
Dan Liston
> Thanks to all the useful suggestions that were offered regarding the
> .org.org error messages. Dan, you suggested that restarting named and
> sendmail might be worth a try. I use ssh to log in to the FreeBSD server at
> Interland where I can get root access but the server is shared as are some
> of the programs. Is there a safe command line way to restart named in a
> circumstance like that? Using man I don't see a command listed to use to
> restart it and named isn't listed among the limited set of services that I
> can restart via the administrator's web login.
>
> William Arnold, your message below seems a likely explanation.
> My own /etc/resolv.conf file currently contains just this:
> nameserver localhost
>
> Having read
> http://www.zmailer.org/mhalist/2002/msg00192.html
> and
> http://nscp.upenn.edu/aix4.3html/files/aixfiles/resolv.conf.htm
> (and not understood either of them fully, I wonder whether I should be
> adding a line like this:
> domain ctcnet.org
> to the /etc/resolv.conf file
> According to the second URL above, "The DomainName variable is the name of
> the local Internet domain. If there is no domain or search entry in the
> file, the gethostbyname subroutine returns the default domain (that is,
> everything following the first period). If the host name does not have a
> domain name included, the root domain is assumed."
> So I imagine that since I don't have a domain name variable in resolv.conv,
> perhaps the gethostbyname routine finds my domain ctcnet.org, which is in
> the hosts file, and then everything after the first period (i.e., just .org)
> is then appended to the intended email recipient's address resulting in
> .org.org if their address ends in .org... Is there any risk to changing the
> /etc/resolv.conf file by adding a domain line?
> Sorry that this is getting a bit away from pure majordomo...
> - Steve Ronan
>
> ----- Original Message -----
> From: "William W. Arnold" <warnold@vipnet.org>
> To: "Stephen Ronan" <sronan@ctcnet.org>
> Cc: <majordomo-users@greatcircle.com>
> Sent: Friday, February 21, 2003 12:56 PM
> Subject: Re: .org.org error messages
>
>
>> Stephen Ronan writes ---
>> >> ----- The following addresses had permanent fatal errors -----
>> >><abcabc@abc.org.org>
>> >> (reason: 553 5.3.5 system config error)
>> >>
>> >> ----- Transcript of session follows -----
>> >>553 5.3.5 abc.org.org. config error: mail loops back to me (MX problem?)
>> >>554 5.3.5 Local configuration error
>> >
>> >The closest thing I can find to a clue via google is this message
>> >http://www.zmailer.org/mhalist/2002/msg00192.html
>> >which seems to indicate that something similar can occur if at the
> recipient
>> >end someone's
>> >/etc/resolv.conf file lacks a 'domain' line (whatever that means).
>> >
>> >I'm curious to know whether others of you are seeing .org.org within some
> of
>> >your bounced messages and, if so, whether you may know what the problem
> is
>> >that 's causing that. Thanks for any advice.
>>
>> It happens to me fairly often.
>>
>> What's happening (as far as I can see)
>>
>> 1) the lookup for abc.org failed in such a way that your local
>> nameserver thinks that there's no such domain.
>> 2) In that case, it searches through it's search list of
>> domains to see if it's a local address with the domain truncated.
>> 3) You're at a .org site, so .org is in your search list.
>> 4) so one of the addresses it looks up is abc.org.org
>> 5) Which is a valid host, since the owner of org.org
>> has setup his DNS to return 127.0.0.1 for all lookup attempts
>> to his domain.
>> 6) so your mail server attempts to deliver the mail to itself,
>> detects this and error's out permenently.
>>
>> If 5) wasn't there, then it would bounce with a no such domain error.
>> Of course, abc.org probably does exist, and it was just a DNS error,
>> but the local system can't tell that.
>>
>> You also only see this if your sending system is a .org
>>
>> --
>> -billy- warnold@vipnet.org
>>
>
>
>
Follow-Ups:
|
|
