Host found but no data record of requested type
beast
<Some...@CliffordChance.com>: Host or domain name not found. Name
service error for name=mail.global.frontbridge.com type=A: Host found but
no data record of requested type
From the server itself:
[root]# host mail.global.frontbridge.com
mail.global.frontbridge.com has address 65.55.251.22
What could be the problem?
Steven Wayne
You're using different DNS servers to obtain the information.
What are the contents of the file /etc/resolv.conf on both servers?
Steven.
--
Zounds! I was never so bethumped with words
since I first called my brother's father dad.
-- William Shakespeare, "Kind John"
beast
> You're using different DNS servers to obtain the information.
>
> What are the contents of the file /etc/resolv.conf on both servers?
>
There is only 1 server, so the NS server is same. I guess its because
of diferrent time when the query was made.
But what was the result of the query that makes this error and
who/which server should responsible for this error :)
Thanks.
Wietse Venema
[ Charset ISO-8859-1 unsupported, converting... ]
http://www.postfix.org/DEBUG_README.html#no_chroot
Wietse
Steven Wayne
The result was what you originally posted to this mailing list.
The DNS server is responsible for the answer it gave, but I have no idea
what caused the error.
Steven.
--
... I don't know why but, suddenly, I want to discuss declining I.Q.
LEVELS with a blue ribbon SENATE SUB-COMMITTEE!
beast
> >
> look in /var/spool/postfix/etc/resolv.conf
>
The postfix is _not_ running chrooted. All "n" in master.cf
In fact, this domain was working few days back and just after I
receive the complaint, it works by resending the email.
I still wondering, what answer given by my DNS that causing this error?
[root]# cat /etc/resolv.conf
nameserver 203.153.97.42
nameserver 203.153.118.10
nameserver 202.154.1.2
Steven Wayne
I forget, what was the original posting?
Steven.
--
"In order to make an apple pie from scratch, you must first create the
universe."
-- Carl Sagan, Cosmos
Wietse Venema
> On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > >
> > look in /var/spool/postfix/etc/resolv.conf
> >
>
> The postfix is _not_ running chrooted. All "n" in master.cf
Does the file /var/spool/postfix/etc/resolv.conf file exist?
What is the last read access time?
Wietse
beast
> > On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > > >
> > > look in /var/spool/postfix/etc/resolv.conf
> > >
> >
> > The postfix is _not_ running chrooted. All "n" in master.cf
>
> What is the last read access time?
No. It does not.
[root@blowfish ~]# ls -l /var/spool/postfix/
total 120
drwx------ 2 postfix root 12288 Mar 2 11:10 active
drwx------ 2 postfix root 4096 Mar 2 10:08 bounce
drwx------ 2 postfix root 4096 Apr 27 2005 corrupt
drwx------ 18 postfix root 4096 May 31 2005 defer
drwx------ 18 postfix root 4096 May 31 2005 deferred
drwx------ 2 postfix root 4096 Feb 19 18:01 flush
drwx------ 2 postfix root 4096 Apr 27 2005 hold
drwx------ 2 postfix root 4096 Mar 2 11:10 incoming
drwx-wx--- 2 postfix postdrop 4096 Mar 2 00:11 maildrop
drwxr-xr-x 2 root root 4096 Feb 26 19:21 pid
drwx------ 2 postfix root 4096 Feb 26 20:27 private
drwx--x--- 2 postfix postdrop 4096 Feb 26 20:27 public
drwx------ 2 postfix root 4096 Apr 27 2005 saved
drwx------ 2 postfix root 4096 Apr 27 2005 trace
Thanks.
Wietse Venema
> On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > beast:
> > > On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > > > >
> > > > look in /var/spool/postfix/etc/resolv.conf
> > > >
> > >
> > > The postfix is _not_ running chrooted. All "n" in master.cf
> >
> > Does the file /var/spool/postfix/etc/resolv.conf file exist?
> > What is the last read access time?
>
> No. It does not.
>
> [root@blowfish ~]# ls -l /var/spool/postfix/
> total 120
Then you need to check the file permission of / /etc /etc/resolv.conf
or any other file that's needed for host lookup.
Directories need read and execute permission for NON-ROOT USERS,
files need read permission for NON-ROOT USERS.
Then test the host lookup as an NON-ROOT USER.
If that fails, see if if you're running Apparmor of some other
security enhancing feature that breaks legitimate applications.
Wietse
Wietse Venema
> beast:
> > On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > > beast:
> > > > On 2/28/07, Wietse Venema <wie...@porcupine.org> wrote:
> > > > > >
> > > > > look in /var/spool/postfix/etc/resolv.conf
> > > > >
> > > >
> > > > The postfix is _not_ running chrooted. All "n" in master.cf
> > >
> > > Does the file /var/spool/postfix/etc/resolv.conf file exist?
> > > What is the last read access time?
> >
> > No. It does not.
> >
> > [root@blowfish ~]# ls -l /var/spool/postfix/
> > total 120
Forget it.
I need to see the output from dig for the host in question.
dig a hostname
Wietse
beast
>
> I need to see the output from dig for the host in question.
>
> dig a hostname
[beast@blowfish ~]$ ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 108 Feb 26 20:24 /etc/resolv.conf
[beast@blowfish ~]$ dig mail.global.frontbridge.com
; <<>> DiG 9.2.4 <<>> mail.global.frontbridge.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23886
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 6
;; QUESTION SECTION:
;mail.global.frontbridge.com. IN A
;; ANSWER SECTION:
mail.global.frontbridge.com. 2 IN A 207.46.51.86
;; AUTHORITY SECTION:
frontbridge.com. 169894 IN NS ns15-f.bigfish.com.
frontbridge.com. 169894 IN NS ns16-f.bigfish.com.
frontbridge.com. 169894 IN NS ns17-f.bigfish.com.
frontbridge.com. 169894 IN NS ns8-f.bigfish.com.
frontbridge.com. 169894 IN NS ns9-f.bigfish.com.
frontbridge.com. 169894 IN NS ns10-f.bigfish.com.
;; ADDITIONAL SECTION:
ns8-f.bigfish.com. 157481 IN A 12.129.199.38
ns9-f.bigfish.com. 157481 IN A 216.148.222.38
ns10-f.bigfish.com. 157481 IN A 206.16.192.228
ns15-f.bigfish.com. 142454 IN A 62.209.45.168
ns16-f.bigfish.com. 165555 IN A 207.46.163.21
ns17-f.bigfish.com. 165555 IN A 65.55.251.21
;; Query time: 18 msec
;; SERVER: 203.153.97.42#53(203.153.97.42)
;; WHEN: Fri Mar 2 19:27:11 2007
;; MSG SIZE rcvd: 289
But anyway, the mail was succesfuly delivered after I ask the user to
re-send it.
--beast
Wietse Venema
> But anyway, the mail was succesfuly delivered after I ask the user to
> re-send it.
In that case the DNS problem was temporary.
Wietse
beast
> > But anyway, the mail was succesfuly delivered after I ask the user to
> > re-send it.
>
>
But if the DNS problem was temporary, why postfix gives permanent
error and not simply retry on the next cycle?
Wietse Venema
The error CODE was permanent. The host did not exist in DNS.
The error CAUSE was not. Someone fixed it.
Wietse