Sam Varshavchik wrote: > Simon Loewen writes: > I have no issues resolving dnsexit.com > > [mr...@lc2440 ~]$ testmxlookup dnsexit.com > Domain dnsexit.com: > Relay: mail.dnsexit.com, Priority: 1, Address: ::ffff:67.214.175.80 > Relay: mail2.dnsexit.com, Priority: 2, Address: ::ffff:64.182.102.205 > Hi Sam,
I have set the DNS in /etc/resolv.conf to these servers. After I tested dig and testmxlookup with each server I removed the IP from the file and entered the next server: German Privacy Foundation e.V nameserver 87.118.100.175 OpenDNS nameserver 208.67.222.222 My internet router (Goes to Chello) nameserver 192.168.1.1 My ISPs two nameservers (Chello.nl) nameserver 213.46.228.196 nameserver 62.179.104.196 ALL of these name servers return an answer via dig: ;; QUESTION SECTION: ;dnsexit.com. IN MX ;; ANSWER SECTION: dnsexit.com. 28800 IN MX 2 mail2.dnsexit.com. dnsexit.com. 28800 IN MX 1 mail.dnsexit.com. With each of these nameservers I also ran # /usr/lib/courier/bin/testmxlookup and this always returned: * Soft error. * Please let me know whether you think all the above DNS servers are inappropriate for testing testmxlookup with, and if so please give me a server that I could use for testing? Perhaps, the upstream server that you used to test testmxlookup? S ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
