I'm caught in a technical war between two companies. One is a major email hosting organization. The second is a DNS provider called DNSMadeEasy.
The problem: An email from an outside domain to a domain inside the email host is intermittently delayed for two or more hours. The outside domain uses DNSMadeEasy for hosting and vanity nameservers.
The symptoms: postfix at the email host sends: 450 4.1.8 : Sender address rejected: Domain not found (in reply to RCPT TO command) deferred
It looks like some kind of DNS problem, but both DNSMadeEasy and the email host say there is no problem and point the finger at each other.
One of the techs at the email host passed the following information to me supposedly written by one of the senior techs:
Actually the problem with skv.com is here -- domain resides on
skv.com
ns3.primusnetworks.com
208.80.126.4
ns2.primusnetworks.com
208.80.124.4
ns1.primuscomputing.com
208.94.149.4
Looks like everything is correct, but
1) domain primuscomputing.com is also served by ns1/2.primusnetworks.com,thus we should be asking ns2/3.primusnetworks.com to get address of ns1.primuscomputing.com
2) In turn primusnetworks.com is actually located only on one NS (despite of what root servers think)
primusnetworks.com
ns1.primuscomputing.com
208.94.149.4
This is severe violation of RFC – there should be at least two NS servers for domain.
The worst – this single NS server is not configured correctly.
So finally we see that skv.com is served by single incorrectly configured NS server – skv.com needs to change the DNS hoster.
Additional Note: DNSMadeEasy says that there are SIX independent servers that work for skv.com.
Two Questions:
If you look at how the nameservers are specified for skv.com, do you see a problem?
Do you understand what the mail host is trying to say?
I'm trying to find out more information but both companies are digging their heels in.
From looking at the whois record for skv.com, we can see that only one of the three listed nameservers has a glue record:
We can also see that the one that does have a glue record doesn't match what's in the DNS for that hostname.
So, the domain having been registered via Network Solutions, the place where this needs to be fixed is at Network Solutions, by the owner of skv.com.