On 10/14/2010 2:43 AM, Eugene Grosbein wrote:
Is host(1) supposed to do lookups using suffixes from /etc/resolv.conf
for FQDN with dot at the end?
... if only there were a document of some kind that described how the
tool was supposed to work ... something like a manual ...
:)
Doug
--
Br
On 14.10.2010 13:43, Doug Barton wrote:
>> Hopefully it does not find but what if such names would exist
>> and have MX records? host(1) would lie to me.
>
> No, it would act the way it's supposed to.
Is host(1) supposed to do lookups using suffixes from /etc/resolv.conf
for FQDN with dot at the
On 10/13/2010 12:05 AM, Eugene Grosbein wrote:
On 13.10.2010 01:39, Doug Barton wrote:
I care about my resolver behavior.
Ok, well, that's working as advertised, so no problems then.
That's fine. And how about host(1)?
It looks for MX record for synthetic domain names
using suffixes from /e
On 13.10.2010 01:39, Doug Barton wrote:
>> I care about my resolver behavior.
>
> Ok, well, that's working as advertised, so no problems then.
That's fine. And how about host(1)?
It looks for MX record for synthetic domain names
using suffixes from /etc/resolv.conf
Hopefully it does not find bu
On Tue, 12 Oct 2010, Tom Evans wrote:
> On Tue, Oct 12, 2010 at 3:39 PM, Ian Smith wrote:
> > On Tue, 12 Oct 2010, Tom Evans wrote:
> > > On Tue, Oct 12, 2010 at 10:05 AM, Ian Smith
> > wrote:
[..]
> > > > If a domain has no MX server, how's an MTA supposed to do mail with
> > it?
> >
On 10/12/2010 5:34 AM, Eugene Grosbein wrote:
On 12.10.2010 14:10, Doug Barton wrote:
It's a pity if we have no diagnostic utility that behaves just like
ordinary applications like MTA dealing with DNS... How am I supposed
to debug suspected MTA behavior without such utility?
Step 1, verify t
On Oct 12, 2010, at 8:30 AM, Tom Evans wrote:
>> Taking the '5.3. Master file example' in RFC1035, what is the A response
>> for 'ISI.EDU.' where the domain itself has no specific A RR? Would it
>> be that of VENERA.ISI.EDU, or that of the first A listed, ie A.ISI.EDU?
>
> That domain has an MX r
On Oct 12, 2010, at 9:30 AM, Tom Evans wrote:
[ ... ]
> Thats what I said wasn't it?
>
> Oh wait, I missed the words 'If we assume it doesn't have an MX record' :/
Yep. Perhaps we are in violent agreement...? :-)
--
-Chuck
___
freebsd-net@freebsd.o
On Tue, Oct 12, 2010 at 5:22 PM, Chuck Swiger wrote:
> No, it would use the published MX records for the domain, and would first try
> delivering to vapor.isi.edu as the lowest precedence MX host listed:
Thats what I said wasn't it?
Oh wait, I missed the words 'If we assume it doesn't have an M
On Tue, Oct 12, 2010 at 3:39 PM, Ian Smith wrote:
> On Tue, 12 Oct 2010, Tom Evans wrote:
> > On Tue, Oct 12, 2010 at 10:05 AM, Ian Smith wrote:
> > > On Mon, 11 Oct 2010, Eugene Grosbein wrote:
> > > > Hi!
> > > >
> > > > FreeBSD 8.1-STABLE:
> > > >
> > > > # host koin-nkz.com.
> >
On Tue, 12 Oct 2010, Tom Evans wrote:
> On Tue, Oct 12, 2010 at 10:05 AM, Ian Smith wrote:
> > On Mon, 11 Oct 2010, Eugene Grosbein wrote:
> > > Hi!
> > >
> > > FreeBSD 8.1-STABLE:
> > >
> > > # host koin-nkz.com.
> > > koin-nkz.com has address 62.231.164.101
> > > Host koin-nkz.co
On 12.10.2010 14:10, Doug Barton wrote:
>> It's a pity if we have no diagnostic utility that behaves just like
>> ordinary applications like MTA dealing with DNS... How am I supposed
>> to debug suspected MTA behavior without such utility?
>
> Step 1, verify that your authoritative name servers h
On 12.10.2010 16:05, Ian Smith wrote:
> > # host koin-nkz.com.
> > koin-nkz.com has address 62.231.164.101
> > Host koin-nkz.com not found: 3(NXDOMAIN)
> >
> > This domain does not have MX records but NXDOMAIN seems to wrong return
> > code to me. Think about MTA that does look-up for MX fi
On Tue, Oct 12, 2010 at 10:05 AM, Ian Smith wrote:
> On Mon, 11 Oct 2010, Eugene Grosbein wrote:
> > Hi!
> >
> > FreeBSD 8.1-STABLE:
> >
> > # host koin-nkz.com.
> > koin-nkz.com has address 62.231.164.101
> > Host koin-nkz.com not found: 3(NXDOMAIN)
> >
> > This domain does not have MX r
On Mon, 11 Oct 2010, Eugene Grosbein wrote:
> Hi!
>
> FreeBSD 8.1-STABLE:
>
> # host koin-nkz.com.
> koin-nkz.com has address 62.231.164.101
> Host koin-nkz.com not found: 3(NXDOMAIN)
>
> This domain does not have MX records but NXDOMAIN seems to wrong return
> code to me. Think about
On 10/11/2010 8:32 PM, Eugene Grosbein wrote:
On 11.10.2010 18:05, Hajimu UMEMOTO wrote:
egrosbein> Is it a bug in our resolver?
I think no, host(1) links ISC's resolver, and it doesn't use libc's
resolver. I suspect there is some problem in host(1) or ISC's
resolver.
Is there a command ca
On 11.10.2010 18:05, Hajimu UMEMOTO wrote:
> egrosbein> Is it a bug in our resolver?
>
> I think no, host(1) links ISC's resolver, and it doesn't use libc's
> resolver. I suspect there is some problem in host(1) or ISC's
> resolver.
Is there a command capable of looking up MX records and
linked
Hi,
> On Mon, 11 Oct 2010 13:31:04 +0700
> Eugene Grosbein said:
egrosbein> FreeBSD 8.1-STABLE:
egrosbein> # host koin-nkz.com.
egrosbein> koin-nkz.com has address 62.231.164.101
egrosbein> Host koin-nkz.com not found: 3(NXDOMAIN)
egrosbein> This domain does not have MX records but NXD
Hi!
FreeBSD 8.1-STABLE:
# host koin-nkz.com.
koin-nkz.com has address 62.231.164.101
Host koin-nkz.com not found: 3(NXDOMAIN)
This domain does not have MX records but NXDOMAIN seems to wrong return
code to me. Think about MTA that does look-up for MX first,
obtains NXDOMAIN and rejects mail.
tc
19 matches
Mail list logo
