Is this error just Demon being very picky in some way or is it
something more than that? :-
Final-Recipient: rfc822; uk...@sandj.demon.co.uk
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host punt-2.mail.demon.net[194.217.242.75] said:
550-Verification failed for <ch...@home.isbd.net> 550-Unrouteable address
550 Sender verify failed (in reply to RCPT TO command)
The domain home.isbd.net is a sub-domain of my domain isbd.net,
isbd.net is hosted at BsNet but home.isbd.net is my home linux machine
where postfix is running. home.isbd.net has a static IP address.
Generally mail sent out from home.isbd.net works OK.
--
Chris Green
home.ibsd.net has no records in any DNS servers authorative for ibsd.net
use "dig" to do queries.
I used this method to find this out.
host> dig @d.gtld-servers.net ibsd.net
; <<>> DiG 9.2.4 <<>> @d.gtld-servers.net ibsd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1442
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 3
;; QUESTION SECTION:
;ibsd.net. IN A
;; AUTHORITY SECTION:
ibsd.net. 172800 IN NS ns.ibsd.net.
ibsd.net. 172800 IN NS ns.twinwave.net.
ibsd.net. 172800 IN NS ns2.ibsd.net.
;; ADDITIONAL SECTION:
ns.ibsd.net. 172800 IN A 62.214.121.34
ns.twinwave.net. 172800 IN A 195.96.32.22
ns2.ibsd.net. 172800 IN A 62.214.121.56
;; Query time: 145 msec
;; SERVER: 192.31.80.30#53(d.gtld-servers.net)
;; WHEN: Mon Aug 1 11:38:12 2005
;; MSG SIZE rcvd: 135
this shows three name servers are responsible for your domain.
querying these nameservers....
host> dig @ns.ibsd.net ANY home.ibsd.net
gives nothing
host> dig @ns2.ibsd.net ANY home.ibsd.net
gives nothing
host> dig @ns.twinwave.net ANY home.ibsd.net
also gives nothing. So it appears the subdomain doesn't exist.
querying the top level gives us all this info
host> dig @ns.ibsd.net ANY ibsd.net
; <<>> DiG 9.2.4 <<>> @ns.ibsd.net ANY ibsd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1842
;; flags: qr aa rd; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 4
;; QUESTION SECTION:
;ibsd.net. IN ANY
;; ANSWER SECTION:
ibsd.net. 86400 IN SOA ns.ibsd.net.
hostmaster.ibsd.net. 2005062201 10800 3600 604800 86400
ibsd.net. 86400 IN A 62.214.121.51
ibsd.net. 86400 IN NS ns2.ibsd.net.
ibsd.net. 86400 IN NS ns.ibsd.net.
ibsd.net. 86400 IN NS ns.twinwave.net.
ibsd.net. 86400 IN MX 20 mx1.ibsd.net.
ibsd.net. 86400 IN MX 10 mx0.ibsd.net.
;; ADDITIONAL SECTION:
ns.ibsd.net. 86400 IN A 62.214.121.34
ns2.ibsd.net. 86400 IN A 62.214.121.56
mx0.ibsd.net. 86400 IN A 62.214.121.44
mx1.ibsd.net. 86400 IN A 62.214.121.55
;; Query time: 52 msec
;; SERVER: 62.214.121.34#53(ns.ibsd.net)
;; WHEN: Mon Aug 1 11:42:01 2005
;; MSG SIZE rcvd: 254
So add A and MX records for your subdomain to the zones of these nameservers or
re-delegate your subdomain to a nameserver on your system.
HTH
Rob
--
Rap it up for the common good
Let us enlist the neighbourhood
It's OK, I've overstood
This is a wordy rappinghood. OK, bye.
Tomtomclub, 1980.
A 'dig home.isbd.net' gives:-
; <<>> DiG 9.2.4rc4 <<>> home.isbd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2719
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION:
;home.isbd.net. IN A
;; ANSWER SECTION:
home.isbd.net. 86356 IN A 84.51.144.229
;; AUTHORITY SECTION:
isbd.net. 63260 IN NS dns0.bsnet.co.uk.
isbd.net. 63260 IN NS dns1.bsnet.co.uk.
isbd.net. 63260 IN NS dns2.bsnet.co.uk.
;; Query time: 1 msec
;; SERVER: 193.109.193.33#53(193.109.193.33)
;; WHEN: Mon Aug 1 11:53:30 2005
;; MSG SIZE rcvd: 115
A 'dig @d.gtld-servers.net home.isbd.net' gives:-
; <<>> DiG 9.2.4rc4 <<>> @d.gtld-servers.net home.isbd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62996
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 1
;; QUESTION SECTION:
;home.isbd.net. IN A
;; AUTHORITY SECTION:
isbd.net. 172800 IN NS foundation.bsnet.co.uk.
isbd.net. 172800 IN NS ns1.futile.net.
;; ADDITIONAL SECTION:
ns1.futile.net. 172800 IN A 82.133.91.21
;; Query time: 115 msec
;; SERVER: 192.31.80.30#53(d.gtld-servers.net)
;; WHEN: Mon Aug 1 11:54:27 2005
;; MSG SIZE rcvd: 108
I don't quite understand why they're different but both seem to be
able to find A records for home.isbd.net.
--
Chris Green
Shit, My bad! Sorry.
OK then, now i've got the right domain...
host> dig @b.gtld-servers.net ANY isbd.net
; <<>> DiG 9.2.4 <<>> @b.gtld-servers.net ANY isbd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1248
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1
;; QUESTION SECTION:
;isbd.net. IN ANY
;; ANSWER SECTION:
isbd.net. 172800 IN NS foundation.bsnet.co.uk.
isbd.net. 172800 IN NS ns1.futile.net.
;; AUTHORITY SECTION:
isbd.net. 172800 IN NS foundation.bsnet.co.uk.
isbd.net. 172800 IN NS ns1.futile.net.
;; ADDITIONAL SECTION:
ns1.futile.net. 172800 IN A 82.133.91.21
;; Query time: 287 msec
;; SERVER: 192.33.14.30#53(b.gtld-servers.net)
;; WHEN: Tue Aug 2 12:03:23 2005
;; MSG SIZE rcvd: 131
shows two nameservers which are responsible for isbd.net
querying them for any isbd.net records shows this.
host> dig @foundation.bsnet.co.uk ANY isbd.net
; <<>> DiG 9.2.4 <<>> @foundation.bsnet.co.uk ANY isbd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 847
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 3, ADDITIONAL: 6
;; QUESTION SECTION:
;isbd.net. IN ANY
;; ANSWER SECTION:
isbd.net. 86400 IN A 82.133.91.150
isbd.net. 86400 IN MX 10 zippy.x-1.net.
isbd.net. 86400 IN MX 100 mx0.x-1.net.
isbd.net. 86400 IN MX 100 mx1.x-1.net.
isbd.net. 86400 IN NS dns0.bsnet.co.uk.
isbd.net. 86400 IN NS dns1.bsnet.co.uk.
isbd.net. 86400 IN NS dns2.bsnet.co.uk.
isbd.net. 86400 IN SOA dns0.bsnet.co.uk.
root.bsnet.co.uk. 2004030901 28800 3600 604800 86400
;; AUTHORITY SECTION:
isbd.net. 86400 IN NS dns0.bsnet.co.uk.
isbd.net. 86400 IN NS dns1.bsnet.co.uk.
isbd.net. 86400 IN NS dns2.bsnet.co.uk.
;; ADDITIONAL SECTION:
zippy.x-1.net. 900 IN A 82.133.91.134
mx0.x-1.net. 86400 IN A 212.135.230.210
mx1.x-1.net. 86400 IN A 212.135.230.215
dns0.bsnet.co.uk. 86400 IN A 82.133.91.19
dns1.bsnet.co.uk. 86400 IN A 82.133.91.20
dns2.bsnet.co.uk. 86400 IN A 212.135.230.213
;; Query time: 37 msec
;; SERVER: 82.133.91.131#53(foundation.bsnet.co.uk)
;; WHEN: Tue Aug 2 12:05:50 2005
;; MSG SIZE rcvd: 355
with the same set from ns1.futile.net
asking these nameservers for any home.isbd.net records shows
host> dig @ns1.futile.net ANY home.isbd.net
; <<>> DiG 9.2.4 <<>> @ns1.futile.net ANY home.isbd.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1019
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUESTION SECTION:
;home.isbd.net. IN ANY
;; ANSWER SECTION:
home.isbd.net. 86400 IN A 84.51.144.229
;; AUTHORITY SECTION:
isbd.net. 86400 IN NS dns0.bsnet.co.uk.
isbd.net. 86400 IN NS dns1.bsnet.co.uk.
isbd.net. 86400 IN NS dns2.bsnet.co.uk.
;; ADDITIONAL SECTION:
dns0.bsnet.co.uk. 86400 IN A 82.133.91.19
dns1.bsnet.co.uk. 86400 IN A 82.133.91.20
dns2.bsnet.co.uk. 86400 IN A 212.135.230.213
;; Query time: 37 msec
;; SERVER: 82.133.91.21#53(ns1.futile.net)
;; WHEN: Tue Aug 2 12:07:05 2005
;; MSG SIZE rcvd: 163
So these nameservers can give us an A record for home.isbd.net but not an MX record
So add an MX record in the nameservers to show something like
home.isbd.net IN MX 5 home.isbd.net
> OK then, now i've got the right domain...
>
[snip lots of dig output]
>
> So these nameservers can give us an A record for home.isbd.net but not an MX record
>
> So add an MX record in the nameservers to show something like
>
> home.isbd.net IN MX 5 home.isbd.net
>
>
Sorry to ask another question but I'm not all that knowledgeable about
all this stuff. Where do I need to make this change? It's presumably
not on my home Linux box - or is it?
I do also have access to the zone file on the hosting system via a web
interface, when I look at the zone file for isbd.net it shows me the
following:-
; This is a generic domain template
;
$TTL 86400
@ IN SOA ns0.futile.net. root.futile.net. (
2003011901 ; serial
28800 ; refresh
3600 ; retry
604800 ; expiry
86400 ) ; minimum
;
IN NS ns0.futile.net.
IN NS ns1.futile.net.
IN MX 10 mx1.mail.bsnet.co.uk.
IN MX 100 foundation.bsnet.co.uk.
IN MX 200 relay.bsnet.co.uk.
; IN A ip.address.of.host
;
localhost IN A 127.0.0.1
; this is a commented out line
This doesn't look right to me, I'm sure it *used* to have something
about isbd.net in it but it looks as if it's just a template now with no
real configuration in it. The sysadmin of the hosting system is very
friendly and helpful so if something does need doing there I can ask
him easily enough.
Thanks very much for all your help, it's much appreciated.
--
Chris Green
That's a matter of responsibility delegation ( in DNS terms ).
my previous solution was to provide an MX record for home.isbd.net in the dns
servers for isbd.net
this shows that whilst holding the responsibility for isbd.net they can also
serve for home.ibsd.net
this is the most practical scenario becasue home.isbd.net is a host in the
isbd.net domain.
So these changes need to go in the zone file at the primary nameserver for
isbd.net - It is impossible for me to tell which system this, you should ask
Chris Needham or Paul Rogers about this. :)
Once the MX record is in the primary, the secondaries should transfer the info
from that.
If you wanted to be fly and provide all the records for home.isbd.net yourself
from your linux box you
1. remove ALL records regarding home.isbd.net from the primary
2. add NS records to "delegate" home.isbd.net to your own system
3. configure bind or djbdns to serve A,SOA, and MX records (minimum) for
home.isbd.net
( this means ns1.futile.net know nothing about home.isbd.net apart from the fact
another nameserver is responsible for it )
If you are on a DSL line then the most resilient way to do this is to sign up
for 2 free secondary DNS provision from one fo the many providers such as
granite canyon or the like and specify one from each of these nameservers to be
authorative for home.isbd.net
The cunning part is that these free secondary dns providers are all secondaries
and so pull the information off a primary periodically (your adsl dns system)
however your primary dns system is never advertised and so you get a hidden
primary configuarion which is more resilient by using more stable secondaries.
neat huh?
so the only records in ns1.futile.net for example would be something like
home.isbd.net IN NS ns1.granitecanyon.net
home.isbd.net IN NS ns1.free-secondary-dns.invalid
Although this is a neat example,
If you can get to the primary records for isbd.net - which you must have had at
some point to have A record provision - adding a single MX record is simplest :)
I recommend the orielly DNS book for further reading :)
>
> I do also have access to the zone file on the hosting system via a web
> interface, when I look at the zone file for isbd.net it shows me the
> following:-
>
> ; This is a generic domain template
> ;
> $TTL 86400
> @ IN SOA ns0.futile.net. root.futile.net. (
> 2003011901 ; serial
> 28800 ; refresh
> 3600 ; retry
> 604800 ; expiry
> 86400 ) ; minimum
> ;
> IN NS ns0.futile.net.
> IN NS ns1.futile.net.
> IN MX 10 mx1.mail.bsnet.co.uk.
> IN MX 100 foundation.bsnet.co.uk.
> IN MX 200 relay.bsnet.co.uk.
> ; IN A ip.address.of.host
> ;
> localhost IN A 127.0.0.1
> ; this is a commented out line
>
> This doesn't look right to me,
me neither - have you pasted this verbatim?
I'm sure it *used* to have something
> about isbd.net in it but it looks as if it's just a template now with no
> real configuration in it.
Yep looks that way....
The sysadmin of the hosting system is very
> friendly and helpful so if something does need doing there I can ask
> him easily enough.
ask hime for an MX record to route mail destined for home.isbd.net to home.isbd.net
>
> Thanks very much for all your help, it's much appreciated.
>
No problem
[snip lots more useful help and advice]
Thanks again for all your help.
--
Chris Green