Have you checked basic things like...
the firewall on the mailserver is allowing port 53 tcp/udp
the time on the mailserver is correct
Ben
On 08/10/2012 11:25 PM, li...@sbt.net.au wrote:
have a mail server on netregistry network using
ns1/ns2/ns3.netregistry,net nameservers, all's well,
On Sun, August 12, 2012 9:47 am, Kyle wrote:
If Verizon are claiming they are receiving a Domain Not Found error
_and_ you are certain your domains are correctly configured,
then isn't the problem likely to lie with Net Registry?
The domains are 'hosted' (on a DNS basis) with them. Ergo they
More things to try:
1. Check that reverse DNS records point back correctly.
2. There are web sites to let you prob your DNS servers from a few dozens
of servers around the world. Try using them to check availability.
On Aug 11, 2012 12:28 AM, li...@sbt.net.au wrote:
On Sat, August 11, 2012 12:04
On Sat, August 11, 2012 10:20 pm, Amos Shapira wrote:
More things to try:
1. Check that reverse DNS records point back correctly.
2. There are web sites to let you prob your DNS servers from a few dozens
of servers around the world. Try using them to check availability. On Aug
11, 2012 12:28
This might be a bit simplistic but;
If Verizon are claiming they are receiving a Domain Not Found error
_and_ you are certain your domains are correctly configured,
then isn't the problem likely to lie with Net Registry?
The domains are 'hosted' (on a DNS basis) with them. Ergo they are
On Sun, August 12, 2012 9:47 am, Kyle wrote:
This might be a bit simplistic but;
If Verizon are claiming they are receiving a Domain Not Found error
_and_ you are certain your domains are correctly configured,
then isn't the problem likely to lie with Net Registry?
Kyle, thanks
yes, that's
have a mail server on netregistry network using
ns1/ns2/ns3.netregistry,net nameservers, all's well, EXCEPT:
some remote servers won't accept our mail with Domain not found reject:
any thoughts on how to trouble shoot this further ?
changing to non-netregistry nameservers allowed queued up
On Sat, August 11, 2012 12:04 am, Glen Turner wrote:
1) Verify operation by walk down the name server tree using dig
Firstly, find the nameserver. You are following the tree down so the IP
addresses come from the answers of the previous command:
dig +norecurse ns au
dig @58.65.254.73
Morning All,
I have mananged to get tinydns working perfectly for local domains
however it isn't resolving any external domains. I was wondering if
there were any people out there with knowledge of tinydns and could
through me a tip as to how to get it to resolve all domains.
Cheers,
Adam.
PS.
On 03 Jun 2003 08:20:52 +1000, Adam Hewitt [EMAIL PROTECTED] wrote:
I have mananged to get tinydns working perfectly for local domains
however it isn't resolving any external domains. I was wondering if
there were any people out there with knowledge of tinydns and could
through me a tip as to
This one time, at band camp, Peter Hardy wrote:
On 03 Jun 2003 08:20:52 +1000, Adam Hewitt [EMAIL PROTECTED] wrote:
I have mananged to get tinydns working perfectly for local domains
however it isn't resolving any external domains. I was wondering if
there were any people out there with
On Tue, Jun 03, 2003, Jamie Wilkinson wrote:
And if you're stuck not using bind in resolver-only mode, and since
you've already got djb turds on your system, then you can use djb's
dnscache as your resolver. Together, dnscache and tinydns can work to
behave like bind.
I haven't used them
12 matches
Mail list logo
