Discussion:
name service error
(too old to reply)
Luc Verschraegen
2003-10-14 15:11:21 UTC
Permalink
Hi,

linux redhat 9
postfix postfix-1.1.11

Can't figure out what's going wrong.

when I sent mail to ***@host everything works fine, when I sent mail to
***@host.sub where sub is one of our subdomains I got a "name service
error".

no problem with dig or nslookup

/etc/resolv.conf and /var/spool/postfix/etc/resolv.conf are identical

domain ugent.be
nameserver 157.193.30.47 (our primary DNS server)
options ndots:2

no [named] active

--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
E-mail: ***@UGent.be Fax: +32-(0)9-2644994
--------------------------------------------------------------------------
Wietse Venema
2003-10-14 15:16:09 UTC
Permalink
Post by Luc Verschraegen
Hi,
linux redhat 9
postfix postfix-1.1.11
Can't figure out what's going wrong.
error".
What is THE FULL TEXT of the error message? This includes the type
of DNS lookup (A or MX), the name being looked up, and the nature
of the error.
Post by Luc Verschraegen
no problem with dig or nslookup
What was the QUERY TYPE that you used? A typical beginner's error
is to do type A lookups by hand, while MTAs must do MX lookups.

Wietse
Post by Luc Verschraegen
/etc/resolv.conf and /var/spool/postfix/etc/resolv.conf are identical
domain ugent.be
nameserver 157.193.30.47 (our primary DNS server)
options ndots:2
no [named] active
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
Luc Verschraegen
2003-10-14 15:30:26 UTC
Permalink
Post by Wietse Venema
Post by Luc Verschraegen
Hi,
linux redhat 9
postfix postfix-1.1.11
Can't figure out what's going wrong.
error".
What is THE FULL TEXT of the error message? This includes the type
of DNS lookup (A or MX), the name being looked up, and the nature
of the error.
Post by Luc Verschraegen
no problem with dig or nslookup
What was the QUERY TYPE that you used? A typical beginner's error
is to do type A lookups by hand, while MTAs must do MX lookups.
it was a A record lookup, with set type=MX I get the MX records of our
domain back,

--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
E-mail: ***@UGent.be Fax: +32-(0)9-2644994
--------------------------------------------------------------------------
Post by Wietse Venema
Wietse
Post by Luc Verschraegen
/etc/resolv.conf and /var/spool/postfix/etc/resolv.conf are identical
domain ugent.be
nameserver 157.193.30.47 (our primary DNS server)
options ndots:2
no [named] active
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
Wietse Venema
2003-10-14 15:33:25 UTC
Permalink
Post by Luc Verschraegen
Post by Wietse Venema
Post by Luc Verschraegen
Hi,
linux redhat 9
postfix postfix-1.1.11
Can't figure out what's going wrong.
error".
What is THE FULL TEXT of the error message? This includes the type
of DNS lookup (A or MX), the name being looked up, and the nature
of the error.
% dig any host.sub

; <<>> DiG 8.2 <<>> any host.sub
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4

Right, so I can't help you.

Wietse
Post by Luc Verschraegen
Post by Wietse Venema
Post by Luc Verschraegen
no problem with dig or nslookup
What was the QUERY TYPE that you used? A typical beginner's error
is to do type A lookups by hand, while MTAs must do MX lookups.
it was a A record lookup, with set type=MX I get the MX records of our
domain back,
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
Post by Wietse Venema
Wietse
Post by Luc Verschraegen
/etc/resolv.conf and /var/spool/postfix/etc/resolv.conf are identical
domain ugent.be
nameserver 157.193.30.47 (our primary DNS server)
options ndots:2
no [named] active
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
Luc Verschraegen
2003-10-14 16:11:36 UTC
Permalink
Post by Wietse Venema
Post by Luc Verschraegen
Post by Wietse Venema
Post by Luc Verschraegen
Hi,
linux redhat 9
postfix postfix-1.1.11
Can't figure out what's going wrong.
error".
What is THE FULL TEXT of the error message? This includes the type
of DNS lookup (A or MX), the name being looked up, and the nature
of the error.
ok,

Oct 14 10:11:50 cypress postfix/smtp[3801]: 379D2262DAD: to=<***@admserv.admin>, relay=none, delay=0, status=bounced (Name service error for admserv.admin: Host not found)




$ dig +search any admserv.admin

; <<>> DiG 9.2.1 <<>> +search any admserv.admin
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37845
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: 6

;; QUESTION SECTION:
;admserv.admin.ugent.be. IN ANY

;; ANSWER SECTION:
admserv.admin.ugent.be. 86400 IN A 157.193.71.1
admserv.admin.ugent.be. 86400 IN MX 40 dobit2.ugent.be.
admserv.admin.ugent.be. 86400 IN MX 10 admserv.admin.ugent.be.
admserv.admin.ugent.be. 86400 IN MX 30 mserv.ugent.be.

;; AUTHORITY SECTION:
ugent.be. 86400 IN NS allserv.ugent.be.
ugent.be. 86400 IN NS ns.belnet.be.
ugent.be. 86400 IN NS ugdns1.ugent.be.
ugent.be. 86400 IN NS ugdns2.ugent.be.
ugent.be. 86400 IN NS ugdns3.ugent.be.

;; ADDITIONAL SECTION:
mserv.ugent.be. 86400 IN A 157.193.40.40
dobit2.ugent.be. 86400 IN A 157.193.42.8
ugdns1.ugent.be. 86400 IN A 157.193.40.37
ugdns2.ugent.be. 86400 IN A 157.193.40.42
ugdns3.ugent.be. 86400 IN A 157.193.71.1
allserv.ugent.be. 86400 IN A 157.193.40.41

;; Query time: 2 msec
;; SERVER: 157.193.40.37#53(157.193.40.37)
;; WHEN: Tue Oct 14 17:41:52 2003
;; MSG SIZE rcvd: 322



Luc.
Post by Wietse Venema
% dig any host.sub
; <<>> DiG 8.2 <<>> any host.sub
;; res options: init recurs defnam dnsrch
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
Right, so I can't help you.
Wietse
Post by Luc Verschraegen
Post by Wietse Venema
Post by Luc Verschraegen
no problem with dig or nslookup
What was the QUERY TYPE that you used? A typical beginner's error
is to do type A lookups by hand, while MTAs must do MX lookups.
it was a A record lookup, with set type=MX I get the MX records of our
domain back,
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
Post by Wietse Venema
Wietse
Post by Luc Verschraegen
/etc/resolv.conf and /var/spool/postfix/etc/resolv.conf are identical
domain ugent.be
nameserver 157.193.30.47 (our primary DNS server)
options ndots:2
no [named] active
--------------------------------------------------------------------------
Luc Verschraegen Phone: +32-(0)9-2644732
--------------------------------------------------------------------------
V***@morganstanley.com
2003-10-14 16:22:58 UTC
Permalink
On Wed, 15 Oct 2003, Luc Verschraegen wrote:


Postfix does not use "+search".
Post by Luc Verschraegen
$ dig +search any admserv.admin
--
Viktor.
Continue reading on narkive:
Loading...