Charles Cazabon wrote:
Kyle Wheeler <kyle-qmail@memoryhole.net> wrote:
On Thursday, May 3 at 12:12 AM, quoth Samuel Murez:
His resolv.conf points to 192.168.0.1. If that's not the IP of his
machine, then he's likely not using his locally installed djbdns...
Should I just change it to 127.0.0.1 (the machine is 192.168.0.5) ? Don't
I risk breaking some other things ?
It depends on how you set up your copy of djbdns. If you have it
listening to 127.0.0.1, then yes, just change the first line of your
resolv.conf to 'nameserver 127.0.0.1'.
It will not break anything, provided that your djbdns cache isn't
broken, is running, is listening to the loopback interface
(127.0.0.1), and can resolve names (i.e. that you don't have any funky
network restrictions preventing it from doing its job).
The OP should probably test this first, by running:
DNSCACHEIP=127.0.0.1 dnsqr mx hotmail.com
etc.
On the first try I got this :
[root@yoruban root]# DNSCACHEIP=127.0.0.1 dnsqr mx hotmail.com
15 hotmail.com:
connection refused
then a few seconds later :
[root@yoruban root]# DNSCACHEIP=127.0.01 dnsqr mx hotmail.com
15 hotmail.com:
301 bytes, 1+4+0+12 records, response, noerror
query: 15 hotmail.com
answer: hotmail.com 2237 MX 5 mx3.hotmail.com
answer: hotmail.com 2237 MX 5 mx1.hotmail.com
answer: hotmail.com 2237 MX 5 mx2.hotmail.com
answer: hotmail.com 2237 MX 5 mx4.hotmail.com
additional: mx1.hotmail.com 2237 A 65.54.244.136
additional: mx4.hotmail.com 2237 A 65.54.244.232
additional: mx3.hotmail.com 2237 A 65.54.245.72
additional: mx4.hotmail.com 2237 A 65.54.244.104
additional: mx2.hotmail.com 2237 A 65.54.244.40
additional: mx1.hotmail.com 2237 A 65.54.244.8
additional: mx4.hotmail.com 2237 A 65.54.245.104
additional: mx3.hotmail.com 2237 A 65.54.244.200
additional: mx2.hotmail.com 2237 A 65.54.245.40
additional: mx3.hotmail.com 2237 A 65.54.244.72
additional: mx1.hotmail.com 2237 A 65.54.245.8
additional: mx2.hotmail.com 2237 A 65.54.244.168
and subsequent tries were fine also.
Maybe the errors I'm seeing in qmail are due to qmail getting the same
result as me on my first try. What would make these kind of queries only
work on the second and subsequent tries ?
Thanks,
--Sam
|