I guess I wasn't clear. That domain isn't one of mine. It's on the outside.
> Hi again: > here is a dnsstuff.com test for all records for your domain. > > > DNS Lookup: lernerheidenberg.com ALL record > > > Searching for lernerheidenberg.com ALL record at m.root-servers.net > [202.12.27.33]: Got referral to I.GTLD-SERVERS.NET. (zone: com.) [took 195 > ms] > > Searching for lernerheidenberg.com ALL record at I.GTLD-SERVERS.NET. > [192.43.172.30]: Got referral to ns1.lnoahost.com. (zone: > lernerheidenberg.com.) [took 104 ms] > > Searching for lernerheidenberg.com ALL record at ns1.lnoahost.com. > [72.18.78.2]: Timed out. Trying again. > > Searching for lernerheidenberg.com ALL record at ns2.lnoahost.com. > [72.18.78.4]: Timed out. Trying again. > > Searching for lernerheidenberg.com ALL record at ns1.lnoahost.com. > [72.18.78.2]: Timed out. Trying again. > > Searching for lernerheidenberg.com ALL record at ns2.lnoahost.com. > [72.18.78.4]: Timed out. Trying again. > > Searching for lernerheidenberg.com ALL record at ns1.lnoahost.com. > [72.18.78.2]: Timed out. Trying again. > > Searching for lernerheidenberg.com ALL record at ns2.lnoahost.com. > [72.18.78.4]: Timed out. Trying again. > > > Looks like there is a problem communicating with you DNS server. > > madmac > > > > Phil Leinhauser wrote: >> I have a customer who is having problems with 1 domain getting or >> sending email. I realize this is a bit OT but I'm at a loss. >> >> The problem is with the DNS and looking for the MX. The domain is >> lernerheidenberg.com. I have bind running locally as a caching server >> going to the root servers and it can't lookup the MX. If I look for >> the A record (mail.lernerheidenberg.com) it can't find that either. I >> have the same problem on my MS DNS servers who also go to the roots. >> >> I can however go to some of the internet DNS test sites and get all >> the correct info. This is really bugging the heck out of me because I >> do understand DNS inside and out, and I can't figure it out. >> >> I have no other domains that have this problem. Can anyone confirm >> some problem here or shed a bit of light? >> >> Thanks, >> Phil > >