nameserver for your domain is malfunctioning
deepdown at packetstorm.nu
Tue Dec 3 21:00:32 UTC 2002
> Bob Lockie wrote:
> > I can get mail sometimes and not others.
> > "The nameserver for your domain is malfunctioning.
> > [linux-dev ph:~] host -t mx lockie.ca
> > Nameserver not responding
> > lockie.ca MX record not found, try again
> > [linux-dev ph:~] host ns.lockie.ca
> > ns.lockie.ca A 184.108.40.206";
> > Here is the zone file for lockie.ca
> > @ IN SOA ns.lockie.ca. postmaster.lockie.ca. (
> > 2002101802 ; serial
> > ; 28800 ; refresh
> > 360 ; refresh
> > 14400 ; retry
> > 3600000 ; expire
> > 86400 ; default_ttl
> > )
> > IN A 220.127.116.11
> > MX 10 mx.lockie.ca.
> > NS ns.lockie.ca.
> > localhost IN A 127.0.0.1
> > mx IN A 18.104.22.168
> > ns IN A 22.214.171.124
> > www IN A 126.96.36.199
> > mail IN A 188.8.131.52
> > sftp IN A 184.108.40.206
> > I have no idea what I did wrong.
> > It works from the inside and most people can send me mail
> > (and this domain can sometimes).
> > It seems to work from the inside.
> > # host -t mx lockie.ca
> > lockie.ca mail is handled by 10 mx.lockie.ca.
> > Can somebody see what I did wrong?
> According to the root servers for TLD .ca there are 2 name
> servers authoritive for lockie.ca:
> lockie.ca. 86400 IN NS ns.synerworks.ca.
> lockie.ca. 86400 IN NS
> You only have 1 DNS configured in your zone for lockie.ca.
In addition to that, the primary server ns.lockie.ca does not anwser
dns queries. So in some cases when some mailserver wants to know the MX
for your domain, (and it asks ns.lockie.ca) it won't get an anwser and
doesn't get delivered.
You must fix your primary DNS.
More information about the bind-users