Hi Eric,
Please see my resolv.conf file settings
search xxx.com (My domain name)
nameserver 127.0.0.1
nameserver 203.211.152.66(My ISP DNS1 and DNS2)
nameserver 210.193.2.66
nameserver 192.168.1.54 (My server ip which is NAT on the router)
On Wed, Feb 19, 2014 at 5:44 AM, Postmaster
Created vpopmail users
root
mailer-daemon
under our virtual domain
Then forwarded
root
mailer-daemon
postmaster
via qmailadmin web interface to my vpopmail account
Now
*** PS : All files within / var/qmail/alias where removed prior to doing the
configs as mentioned
Hi ,
I had similar issue
what I had to do was rem out the other lines.
If you have a reslover set on your server
Only have the 127 address working
eg
*search **xxx.com http://xxx.com**(My domain name)*
*nameserver 127.0.0.1*
# nameserver 203.211.152.66(My ISP DNS1 and DNS2)
# nameserver
That's a good thing to do, but before doing so, be sure your localhost
resolver is running:
# dig @127.0.0.1 qmailtoaster.com
If you're using bind:
# service named status
If you're using pdns-recursor:
# service pdns-recursor status
Do the typical stuff (service X start) to start it, and use
On 02/19/2014 09:43 AM, Eric Shubert wrote:
There's a new script in the forthcoming qmailtoaster-util package that
will set up a localhost resolver for you automagically. You can find it
here:
https://github.com/QMailToaster/qmailtoaster-util/blob/master/qt-install-dns-resolver
I think it works
Is anyone else experiencing a rise in attempted account access over the
past 24 hours?
CJ
--
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
